Re: [whatwg/dom] Shadow: Specify when `slotchange` fires (#447)

> In addition to that, [...] a slotchange event for removal case would be a noise for a slotchange event listener because [...] its assigned nodes is always empty.

That’s a really good point. For example: If I wanted to use the `slotchange` event to remove event listeners I added to slotted children, I wouldn’t have access to them anymore. 

Maybe it’s worth thinking about exposing `removedNodes` in the `slotchage` event somehow. The event comes from an internal MutationObserver, so that data should be available, no? Probably a discussion for a new issue.

Regarding your code sample, @hayatoito, I think that you are right that most implementations iterate over `slot.assignedNodes()` so we wouldn’t need to worry.

> It would be great if we can see a concrete example of the current usage of a slotchange event listener. Do you know that?

I don‘t have any particular examples, no. Again, maybe @sorvell or @kevinpschaaf can help out?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/447#issuecomment-302832918