- From: Philip Jägenstedt <notifications@github.com>
- Date: Wed, 09 Mar 2016 22:27:42 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 10 March 2016 06:29:44 UTC
Yes, a method would have been better, and I understand that nobody objected when this change was made. But the situation we find ourselves in is that nobody can say if or when `Event.path` can be deprecated and removed from Blink. Lacking some way of estimating the compat risk of such a change, there's just no way to proceed. I think the options are: 1. A certainty of getting only a less-than-ideal API, the `event.path` attribute. 2. An x% chance of getting only the nicer API, `event.deepPath()` and a (100-x)% chance of getting both `event.path` and `event.deepPath()`. Because I think *x* is a relatively small number, option 2 looks risky to me. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/428#issuecomment-194693893
Received on Thursday, 10 March 2016 06:29:44 UTC