Re: [w3c/webcomponents] slotchange event should not bubble (#571)

The second event is correct. It is the bubbling phase of the first event. This behavior is intentionally designed. The definition of *composed* event might be complex that we can imagine at first, I guess.

The first event's event path will be: #slot => #innerSlot => #inner's shadow => #inner => #host's shadow. 

Note: #host does not receive an event.

A *composed* event does not mean the event is scoped in the *one* node tree.
A *composed* means the event is scoped in (including) descendant node trees.

For example, that means:
- We don't exclude a #innserSlot from an event path because it is shadow-including descendant of #slot's root.
- We exclude a host node because it is not shadow-including descendant of #slot's root.




-- 
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/571#issuecomment-248539441