Steve Schwartz

This isn't actually true. All jquery-ujs bindings are delegated to the `document`, which is the root node. By the time any jquery-ujs bindings get called, the event has already propagated...

That's a good question. To be honest, it's been a long time since I wrote that code, but if I remember correctly, we needed both `preventDefault` and `stopPropagation` for some...

The browsers I always tested in, at the very least, were the latest official (not beta or preview) versions of: - Chrome - Firefox - Safari - Opera - Internet...

Oh, also, make sure the tests pass in each browser with each version of jQuery supported (which are linked at the top right of the test page layout). And, I...

Sorry for the multiple comments, but regarding this particular ticket, there were certain versions of browsers with certain versions of jQuery where certain behavior didn't work properly unless we actually...

@baxang It is customizable! The event binding is namespaced precisely so you can undelegate specific event bindings as needed, just as you've done here. So this is indeed a great...

I've done something like this for some of my older projects, to upgrade to rails 3, using something like this in my application js: ``` js $j(document).on('ajax:complete', 'a[data-remote][data-update], form[data-remote][data-update], select[data-update]',...

@bcm good points. I'm going to play devil's advocate and just say, that if we did include this, it'd likely be in a way that mimics the `update` attribute from...

Just realized, we never decided on the approach for this. I'd say keep it as is, but move the HTML insertion from the `success` callback to the `complete` callback instead.

Also, if you could write a test for this, that'd be even better and I could pull it in right away. Otherwise, I'll have to write one when I can...