Don't spin up extra run-loops when bubbling events. Fixes #11540

[runspired]

Fixes #11540

[rwjblue]

Seems good to me, @stefanpenner r?

[stefanpenner]

I plan to review in the morning. Unless there is s big rush tonight. If so I can gladly look into shortly

[rwjblue]

No huge rush. Can go into [BUGFIX beta] tomorrow (for 2.1).

[rwjblue]

I kicked sauce labs.

@stefanpenner - Whenever you have a chance, I'd love your 👍 / 👎 here...

[rwjblue]

@stefanpenner - r?

[rwjblue]

@stefanpenner - 👍 / 👎?

[stefanpenner]

This fixes up the immediate concern so 👍

This doesn't prevent bubbling from spawning many loops per user action.

For example:

given the following hierarchy root < a < b < c

if a and b have click handlers, and c returns true, a will gets its own run-loop. This isn't desirable.

@runspired I believe due to how we currently integrate with jQuery prevent ^ in the same micro-task is tricky/not possible. To sort this out, I suspect taking your approach re: home-grown event-dispatcher is key.

[asakusuma]

Thanks @runspired!