Re: [w3c/webcomponents] Need "slotchange" event (#288)

I think the use case matters here. It looks like the all use cases listed here are about updating the UI / rendering to accommodate changes in the distributed nodes, and not so much about updating DOM / API surface for component users.  So it's actually desirable for those updates to not take place until the end of the current task.  I'm also fine with dispatching this event before the next rAF as well.

I don't think inserting at most one mutation record of this type is a good idea because it breaks the fundamental invariant of mutation observers that all mutations are recorded, and that each mutation record allows users to revert and reapply the same mutation elsewhere.

---
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/288#issuecomment-202812657