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

The issue here is that `slot` elements get superfluous `slotchange` events which are of no use. The fact *replace all* is implemented as a sequence of removing each node is more of a spec fiction. The author shouldn't have to deal with it.

In fact, the WebKit team would object to the currently specified behavior.

Note that neither Gecko nor WebKit implement the currently specified behavior, and Chrome doesn't fire `slotchange` in the tree order in other cases. It just so happens to match this particular spec behavior but the order of elements in other cases are not spec conforming.

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