Re: [webcomponents] deepPath's definition is ambiguous when the event path contains a non-Node EventTarget (#432)

Do you mean the following is wrong?

> If both ANCESTOR-A and ANCESTOR-B exist, let's apply "unclosed node" check for them

Using ANCESTOR-A and ANCESTOR-B sounds bad here?
I am not sure 100% how this works. This is just the result of the clarification of @rniwa 's proposal:

> My proposal is to find the first Node event target parent from the current event target, and use that to filter nodes. If there are no such target, don't filter anything (e.g. for events on XHR).




---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/432#issuecomment-202320140

Received on Monday, 28 March 2016 09:30:09 UTC