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

One more thing:
Since calculating composedPath() is not so cheap, Blink caches the result; composedPath() is calculated lazily, but only once. In the 2nd call of composedPath(), it just returns the cached result without relying on the current status. In this sense, Blink is not conforming spec.


-- 
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-340658860

Received on Tuesday, 31 October 2017 04:47:29 UTC