Re: [whatwg/dom] event.composedPath() may return different results if DOM is modified between two calls (#525)

Rough summary from the IRC debate, @rniwa:

* Prefers keeping the status quo.
* Preserving encapsulation at `composedPath()` invocation time is important.
* Keeping dispatch as simple as possible is important for performance.

@smaug----:

* Dislikes the status quo.
* Would prefer storing additional bits during dispatch to make `composedPath()` faster.
* Only concerned about preserving encapsulation at time of dispatch. Non-closed nodes in the event's path that become closed were already revealed.

It seems @domenic would prefer a version where event's path can be disregarded.

-- 
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/525#issuecomment-340704879