Re: [webcomponents] Change deepPath() back to path (a FrozenArray<EventTarget> attribute) (#428)

They are merely the best guesses I'd use if anything were at stake. To justify them somewhat:

10% chance of failure on Option A is because changing the return value after the end of dispatch must be a small minority of the total usage. Most event handlers don't save the event and look at it again later. https://bit.ly/blinkintents lists many small behavioral changes that worked out, many that I'd consider riskier.

80% risk that Event.path will never be removed from Blink is based on the first comment in this thread, that "we have no idea about how risky such a change would be" and thus are stuck. Maybe someone with extreme patience could show it safe using httparchive analysis, or some other new tool, eventually.

20% risk of this spreading due to Blink compat is the most speculative. I want it to be 0%, but it's happened before with IE and WebKit, so doesn't seem too far fetched. Another way it could happen is that Edge has to copy it because they identify as Chrome, and then it's hard to see it ever going away, *even if* it's not implemented elsewhere.

If my guesses seem wildly wrong, or if they aren't even the right things to guess about, I'm also interested in seeing how others see this playing out.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/428#issuecomment-196262764