- From: Ryosuke Niwa <notifications@github.com>
- Date: Wed, 02 Sep 2015 08:24:10 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Wednesday, 2 September 2015 15:25:31 UTC
Okay, now I have a slightly clear picture of what's happening. My comment on https://github.com/w3c/webcomponents/issues/308#issuecomment-137115467 will clarify some confusion about this. On the contrary to what I wrote here, we probably want to expose shadow DOM before composition as is because style rules and inheritance need to be intimately familiar with shadow boundaries and the relationship between trees. I think we should remove the section about the composed tree and how it's used and leave it to [CSS Scoping](https://drafts.csswg.org/css-scoping/#shadow-cascading) to define what it does with it. Shadow DOM spec then just needs to what constitutes a slot and how nodes are distributed into the slot. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/305#issuecomment-137129532
Received on Wednesday, 2 September 2015 15:25:31 UTC