Comments on: .live()

By: Karl Swedberg

Karl Swedberg — Mon, 15 Mar 2010 22:17:38 +0000

All of them are supported now.

* As of jQuery 1.4 the .live() method supports custom events as well as all JavaScript events. As of jQuery 1.4.1 even focus and blur work with live (mapping to the more appropriate, bubbling, events focusin and focusout).
* As of jQuery 1.4.1 the hover event can be specified (mapping to “mouseenter mouseleave”).

By: Wuwu

Wuwu — Mon, 15 Mar 2010 13:09:47 +0000

Im missing a clear list of all supported events.

By: deer421

deer421 — Mon, 15 Mar 2010 09:44:53 +0000

Yet, http://api.jquery.com/jquery/#selector-context says:

"Internally, selector context is implemented with the .find() method, so $('span', this) is equivalent to $(this).find('span')."

By: Karl Swedberg

Karl Swedberg — Mon, 15 Mar 2010 00:24:21 +0000

Sorry, but you're still wrong. Above you'll find that one of the caveats says this:
“DOM traversal methods are not fully supported for finding elements to send to .live(). Rather, the .live() method should always be called directly after a selector, as in the example above.”

By: Karl Swedberg

Karl Swedberg — Mon, 15 Mar 2010 00:23:24 +0000

By: dpbldr

dpbldr — Sun, 14 Mar 2010 13:26:24 +0000

I had the same thing and it appears to be working by using
$('#datepicker').live('mouseover', function(){
$(this).datepicker();
})

By: landonspringer

landonspringer — Sat, 13 Mar 2010 23:24:59 +0000

Hopefully this will save someone the 30 minutes it cost me...

The .live() function will stop propagation if you return false, but this won't work for other bindings on $(document). You have to e.stopImmediatePropagation() to prevent other bindings on $(document) from firing. Example:

$(document).bind('click', function() {
alert('document clicked');
});

$('.some-selector').live('click', function(e) {
e.stopImmediatePropagation();
return false;
});

By: Remus

Remus — Mon, 01 Feb 2010 21:35:27 +0000

When using live() with the “change” event, if the initial value of the element bound to is nothing (element is empty) and you type in a value, the event does not trigger as it should. It only triggers if there is an initial value in there or if the value is changing (duh!) but not when the value is empty and you put a value in for the first time.

Is this a bug or should I use a different event to capture even the first “change”, from empty to a non-empty value?

By: buymeasoda

buymeasoda — Mon, 01 Feb 2010 04:28:40 +0000

Hi,

Could you please update the docs and examples to include details of the new ability to use a context with the live() event.

It was mentioned in the release notes during 14 days of jQuery, but I can't see it presented here in any detail.

From: http://jquery14.com/day-01/jquery-14

live/die now work with context (Commit)

You can now specify a context to the selector that will be used to bind a live event. If you do, only elements under that context will be bound. While the elements themselves do not need to exist when you create the live event, the context must exist.

By: Ryan Parman

Ryan Parman — Thu, 14 Jan 2010 23:34:02 +0000

What arguments are passed back to the callback handler? In JQuery it seemed to be event and selector, but in 1.4 it seems to only be event, where selector is available by digging around.