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

I am happy to defer to implementers here. I had thought they would all be excited about O(1) event dispatch, but perhaps the fact that nobody implemented that so far (and that nobody got sad when we added composedPath(), making it impossible) means that it is not important. For example maybe they've not seen event dispatch being in the critical path for real-world performance.

I think it will have somewhat bad ecosystem effects with regard to XObserver proliferation, but that's already a lost cause, I guess.

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