Re: [w3c/webcomponents] DOM APIs which replace all children end up firing superfluous slotchange events (#764)

Thanks.  So the expected behavior from the author's perspective would be:
```
shadowRoot: <p><slot id="slot1"></slot><b><slot id="slot2"></slot></b><slot id="slot3"></slot></p>
Removing p results in slotchange events on: ["slot1"]
shadowRoot: <p><slot id="slot1"></slot><slot id="slot2"></slot><slot id="slot3"></slot></p>
Setting p.textContent to "" results in slotchange events on: ["slot1"]
```

, right? (Both cases fire a slotchange event only on slot1). I agree that that behavior looks consistent from the autors' perspective.

>From the spec's perspective, can the spec (or maybe the implementation too?) become complicated if we try to align the current spec to the author's expected behavior?

-- 
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/764#issuecomment-418712169