Re: [webcomponents] Slots in a flat tree (#308)

My biggest concerns are:

1. How can we trust the feature of `{display: contents}`? Can we be 100% sure this will be successful? It looks there is no other spec which bets on its success, AFAIK. Shadow DOM looks the only early adapter.

2. Suppose that we support "a slot in a flat tree" in the spec, and developers start to style a slot element, that's *un-reversible* change.
   Later, even if we find "{display: contents}" is not a thing, it's too late. We can not change the behavior without breaking the Web site.

Thus, I have to be careful to add a slot in a flat tree. If we add it, that means that Shadow DOM fails if `{display: contents}` fails.

Is there any significant benefit of adding a slot in a flat tree, which is worth having such a great risk?
Note that we can support "slots in a flat tree" anytime later when we can feel "{display: contents}" is widely accepted.

I am not opposing to "slots in a flat tree", but I am afraid that it's too risky and today is not the day.


@tabatkins, WDTY? Do you have a good feeling that "{display: content}" will succeed??


---
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/308#issuecomment-202256162