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

Oh, Blink is even against the current spec, and the current spec is against, well, sanity :)

When fixing this issue one doesn't need to calculate much during event path creation. Just annotate each event path tuple in a subtree with that subtree's unique "id" and whether that subtree is open or closed.
That is basically flag + a counter. Then just use that information when creating the path lazily.
And by fixing this, composedPath() would always return the same result for the currentTarget, so caching the result would be ok per spec.

So I don't see a reason to not fix this.

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