The propagation was only added to "fake" events, that is, those generated by calling $(...).trigger(); Real events were already bubbling (propagating) natively.
We only normalized event bubbling for all events, by adding it to our fake events. You can always stop the propagation by calling event.stopPropagation (), returning false or using triggerHandler. -- Ariel Flesler http://flesler.blogspot.com On Jan 15, 10:02 am, "Javier Martinez" <ecentin...@gmail.com> wrote: > First of all, thanks to all jQuery members for the new release! is a great > gift! > > With this release, one of the main features is the new event propagation > logic. As I can understand, it seems that, for example, if I have a > div(inside) inside other div(outside) and I attach a click event to the > inside div. The outside div will trigger it's events too... and it's parent, > parent of the parent, etc until it reach the body element. Is this ok? > > If this is the logic, then maybe there is a little overhead on the browser > for a simple event attachment on the most inner div if there is no need for > this propagation (to work like 1.2.6 I mean)... or not? > > Thanks to all!
