No. MooTools garbage collects all the items before it replaces them. On Mon, Dec 15, 2008 at 9:00 AM, rpflo (via Nabble) < ml-user+63492-2030194...@n2.nabble.com<ml-user%2b63492-2030194...@n2.nabble.com> > wrote:
> > Thanks for the replies. I just had a situation where I the event > seemed to be stacking up, while other events were not. > > So am I eating up memory by not destroying the events? > > > On Dec 14, 3:29 am, "El Zorro" > <masked.ban...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1658984&i=0>> > wrote: > > be cautious here - I've witnessed in certain cases Opera will retain it's > > > event handlers between updates resulting in events being fired > successively > > more times with each insert. > > > > Most of the time it's not a problem, but if you notice that behaviour > you'll > > have to call removeEvent before you addEvent. > > > > > > > > On Sun, Dec 14, 2008 at 4:00 AM, rasmusfl0e > > <rasmusf...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1658984&i=1>> > wrote: > > > > > whatever DOM elements you replace you will also loose their respective > > > events. it doesn't matter whether they are replaced by elements > > > matching their tag, id and class. > > > > > either you re-apply the needed events to the new elements or you use > > > event delegation on a static parent element (an element that you are > > > sure won't get replaced). if you're not familiar with event delegation > > > just google it. > > > > > On Dec 12, 5:42 pm, rpflo > > > <rpflore...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1658984&i=2>> > wrote: > > > > So I've got a div named joe in a div named boxingRing. > > > > > > Joe's got a button called dudesFace with a 'click' event (that fires > > > > the function punchDude, but that's irrelevant). > > > > > > If I use Request.HTML and update boxingRing with my new content, > > > > containing a div named craig, > > > > with a new button called dudesFace > > > > and I add a new click event on dudesFace (to punchDude) > > > > > > did the old click event on the old dudesFace die when boxingRing was > > > > updated or if I now click dudesFace will I actually punchDude twice > > > > because I've got two events on it? > > > > > > Basic question is, if a div had elements with events and it gets > > > > updated via Request.HTML, do those events die or will I just keep > > > > filling up the browser's brain with a million events every time I > > > > update the div? > > > ------------------------------ > View message @ > http://n2.nabble.com/Does-Request.HTML-w--update-kill-Events--tp1648584p1658984.html > To start a new topic under MooTools Users, email > ml-node+660466-1583815...@n2.nabble.com<ml-node%2b660466-1583815...@n2.nabble.com> > To unsubscribe from MooTools Users, click here< (link removed) >. > > > ----- The MooTools Tutorial: http://www.mootorial.com www.mootorial.com Clientcide: http://www.clientcide.com www.clientcide.com -- View this message in context: http://n2.nabble.com/Does-Request.HTML-w--update-kill-Events--tp1648584p1659027.html Sent from the MooTools Users mailing list archive at Nabble.com.
