Re: [webcomponents] Composition Algorithm shouldn't unwrap slots (#308)

Given that `{display: contents}` is not well supported in all UAs and it might require a huge amount of rewriting an engine, how about deferring 'including slots in the composed tree' to v2?

Even if we don't have it in v1, we just lose the ability of styling a distributed node by styling a slot. That sounds a small loss. We can consider it again in v2 later.

I'm afraid the worst scenario: We can't ship Shadow DOM v1 soon due to the support cost of `{display: contents}`.


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