Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325)

One thing we need to decide upon is when the post-click-dispatch steps are run. E.g., in Gecko the click event that causes those to be run will still have `eventPhase` set to 2, whereas in Chrome it is 0. http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4568

Both browsers do agree that `currentTarget` is null and only Chrome exposes `composedPath()` at the moment which returns an empty array.

Chrome also allows recursion to happen (stops after 42 times or so) whereas in Firefox the "dispatch flag" is not yet unset and therefore `dispatchEvent()` throws.

I'm inclined to align with Chrome here though that would require taking a copy of event's path as we'd have to set it to null to not reveal anything through `composedPath()`.

-- 
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/325#issuecomment-252923107