Re: [webcomponents] Need "slotting changed" event (#288)

Yeah, AFAIK, we do not have any mechanism to make an event path be *empty* when the target node has a parent node. In other words, a parent node should always receives an event (at capturing phase) when its child node receives an event. We should honor this.

Since we do not want to make a *slotchange* too magical, all we can do here is to make *slotchange* event's *scoped* flag is true. That's the best we can do, if we use an event.

> Speaking about events, if slot elements are part of the composed tree in WebKit, are they part of the event path too then?

Slots and shadow roots can be part of the event path, as per the spec. That's intentionally designed.
In short: event path == (ancestors in the flat tree) + (shadow roots) + (slots)

This section explains why I designed an event path in such a way: http://w3c.github.io/webcomponents/spec/shadow/#event-paths-example


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/288#issuecomment-183716398