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

Yeah, we should consider a case where an event target is not a Node.

We should revise the following sentance:

> Let PATH contain only a node which is an unclosed node of the current target of EVENT.

My rough idea is:

Give A, an event target in the event path, and B, the current target of EVENT:
- If A and B are both Node objects, nothing changes. The current definition should work.
- Otherwise, if A is *traversable* by repeatedly applying [get the parent](https://dom.spec.whatwg.org/#get-the-parent) to B, or vice verse, include A in the deepPath().

Does this sound good?

> Also, what happens if you dispatch a node in a closed shadow tree that might be retargeted, it would be weird for the event path to only contain nodes of the light tree.

This is an intentional behavior. Why do you think this is weird?


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