- From: Philip Jägenstedt <notifications@github.com>
- Date: Wed, 09 Mar 2016 23:52:38 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 10 March 2016 07:53:12 UTC
Having to keep `event.path` in Blink alongside `event.deepPath()` indefinitely while other browsers only support `event.deepPath()` is not a good outcome for interoperability. `event.path` has been shipping since Chrome 35, which went stable in May 2014. That's enough time to worry about breakage when removing it, even if the lack of support hasn't showed up as a compat problem for other engines. Critically, use counters are rendered useless by enumeration, so we have no reliable measure of risk, and inaction is the default. It's not an ideal API, but is it *so* bad that it cannot be salvaged? --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/428#issuecomment-194720492
Received on Thursday, 10 March 2016 07:53:12 UTC