Re: [w3c/webcomponents] [Shadow] Slotting indirect children (#574)

Is there any chance that this could be changed for v1?

The problem with limitation is that there is no acceptable workaround. The only working (but very bad) solution would be to implement something which is very similar to a shadow dom polyfill.

Why is it so tricky to find the shadow to which a node is assigned? I would have suggested the following algorithm:

1. If there is no slot attribute, the node is assigned to the shadow of the direct parent element (if present).
2. If there is a slot attribute set, the node is assigned to the shadow of the direct parent element if present and if it has a slot with this name.
3. If there is a slot attribute set and the direct parent does not have a shadow or the shadow does not have a slot with this name, then it is assigned to the closest shadow with a slot with this name.

For most of the nodes 1. or 2. applies. These nodes will not be slowed down at all. For the remaining other nodes, it will have to check a few additional ancestors.

Do you remember the exact reasons why it didn't make it into the spec?

-- 
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/574#issuecomment-249305053