Hey,
http://brandonaaron.net/docs/livequery/
Destroying events connected to a removed element helps prevent memory
leaks -- it is really the correct behavior.
Well in most cases it probably is. However I actually got my own little
"framework" used by all plugins I wrote, which attaches eve
If you havent seen the livequery plugin, I would recommend looking it over
this would really be the correct solution to this.
http://brandonaaron.net/docs/livequery/
Destroying events connected to a removed element helps prevent memory leaks
it is really the correct behavior.
JK
Hi Felix,
I presume you mean you upgraded from 1.1.3 to 1.2.1. The you're
correct about the change being an "anti-memory leak" fix.
You can do one of two things:
1. Use the native "removeChild()" method (
http://developer.mozilla.org/en/docs/DOM:element.removeChild ). This
won't delete the event
3 matches
Mail list logo