Re: [webcomponents] Remove the constraint that slot can't have another slot as an ancestor (#321)

Yeah, there is no practical benefits. But we have minor bonus, removing the following *special* behavior.

> If a slot element does not satisfy the condition of a slot, it must have the same rendering behavior as the HTMLUnknownElement.

If a slot is used in a document tree:

- No node is assigned to a slot
- Thus, fallback contents are used
- with {display: contents}, which is now being proposed.

Thus, we can get a consistency. No special treatment is required for a slot in a document tree.



---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/321#issuecomment-141381316