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

O(depth) is okay. We have to spend O(depth) cost at any case in event dispatching.

For most kinds of events, we have to traverse a tree up anyway because we can't tell there is no event listener for capture/bubble phase at each node beforehand.

Blink has some optimization for some kind of events so that we can skip event path calculation entirely. But this case is limited.

I'll spend some time later to know how feasible this spec change is for Blink, in terms of performance.

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