Actually it's worse than it appears.
Wontfixing this bug along with bug #10794 causes an unfortunate conflict where I can't fix my existing code to work with jQuery 1.7.1 without breaking backwards compatibility with older jQuery versions. (Which I can't guarantee will never be used in production.)
So now I have to fork my code based on jQuery versions.
Moreover, I have several cases where
.trigger() is what I really really want, and I wanna do
.stopPropagation() only when plugin's
options.noBubble is set to
Again I need to fork the whole
.triggering mechanism based on the value of
Pretty please consider reopening and fixing this bug.
jQuery.Event() is such a neat method and offers such a clean way for advanced triggering of events (custom or not). It a shame to see this bug ruin its elegance and make it all kludgy, all of a sudden.