[whatwg/dom] Consider making dispatchEvent() unset stop (immediate) propagation flags (#219)

If you call stop(Immediate)Propagation() on an event, then try to dispatch the event again, Chrome will not do so.  IE 11 and Gecko both will re-dispatch it, because they unset the flags in dispatchEvent().  The spec currently matches Chrome.  What's the rationale for this?  smaug said <https://bugzilla.mozilla.org/show_bug.cgi?id=698929#c6> he prefers the Gecko/IE behavior.  I don't know why you'd fire the same event twice, so I can't say for sure which makes more sense.  But at first glance I'd think it makes more sense that stopPropagation() cancels the current dispatch, rather than making the event undispatchable in the future.

Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1263937

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/219