Thanks guys, I understand now.
Related question (but maybe for the UI guys)... does anyone know if any
jquery UI components (sortables and dialog in particular) bind events to
something outside their own scope (like by using .live())? I'm guessing
not and that I'm safe instantiating one of tho
On May 30, 2009, at 12:14 PM, Jack Killpatrick wrote:
Thanks, Brandon. So .empty() won't touch events that were bound
using a selector on objects inside what is being emptied, right?
Gotta use .die() to get rid of them?
Yes and no. empty() will unbind events that were bound to the elements
Thanks, Brandon. So .empty() won't touch events that were bound using a
selector on objects inside what is being emptied, right? Gotta use
.die() to get rid of them?
- Jack
Brandon Aaron wrote:
The .live() method binds event handlers at a higher level than the
node(s) selected. So, in other w
The .live() method binds event handlers at a higher level than the
node(s) selected. So, in other words the events aren't actually bound
to specific nodes so they won't be removed when you call empty.
If you need to remove a live event, just call .die(). It is like
.unbind() but for .live() event
I'm guessing that once a .live() instantiation occurs it's there for
good. If that's the case, is there a way to destroy it? (in particular
as it pertains to a selector).
I'm debating using it in a plugin, but am wary because of what could
happen with multiple instances of the plugin and may
5 matches
Mail list logo
