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

Yes. A **slot** has **assigned nodes** (a list of slotables). A **slotable** has an **assigned slot** ( a slot).

The **assign slotables** algorithm updates both those internal variables. (Therefore the node can end up being assigned to the parent when it is inserted into a slot. I don't see a reason to special case fallback content. It should just end up being assigned if there only is fallback content.)

The "slotchange" (going to call it **signal a slot change** most likely) is indeed recursive, but does not need "findSlot", it can simply use the **assigned slot** pointer for recursion.

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