Re: [w3c/webcomponents] Is the order of `slotchange` events along a slot chain across node trees defined? (#617)

I'm not sure I understand step 6.4 of https://dom.spec.whatwg.org/#concept-node-insert. I thought that might've been it, but it doesn't seem to traverse any node trees.

> This has been changed. Right now, a single slotchange event would be dispatched at the “shallowest” slot which is assigned to “deeper” slots.

Do you mean to say that the behavior we see in [the fiddle](https://jsfiddle.net/5rh7g3Lq/) is not specified in https://dom.spec.whatwg.org, and that the behavior will change in a future version of Chrome?

If this is the case (that the `slotchange` event will not propagate down a chain of slots from shallowest to deepest but rather only happen on the slot where **assign slotables** runs), then `slot.assignedNode({flatten:true})` working the way it currently does (or as in https://github.com/w3c/webcomponents/issues/611) will be useless if "deeper" slots have no `slotchange` event by which some custom logic can use `slot.assignedNode({flatten:true})` to determine final-distribution.

-- 
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/617#issuecomment-267724072