This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Although css-scoping spec, 3.3.2. Inheritance [1], explains how the inheritance works for Shadow DOM, I think that should be moved to Shadow DOM spec and should be explained in terms of Composed Tree so that we can make it more strict definition. One more goal is to get rid of the following paragraph from the Shadow DOM spec [2]: > In rendering a document tree, or presenting it visually, the composed tree must be used instead of the document tree. > The composed tree must be updated before the rendering occurs. We should also mention that if a node is not in the composed tree (with document as root), the node doesn't have a CSS layout boxes explicitly. The exact condition of that should be worth considering, though. [1]: http://dev.w3.org/csswg/css-scoping/#inheritance [2]: http://w3c.github.io/webcomponents/spec/shadow/#composed-trees
I think whatever specification defines CSS layout needs to be changed to operate on the composed tree. (I guess we can monkey patch it for now...)
(In reply to Anne from comment #1) > I think whatever specification defines CSS layout needs to be changed to > operate on the composed tree. (I guess we can monkey patch it for now...) Thank you. I wasn't aware of that. Let me investigate further how we can monkey patch it for now.
Fixed at https://github.com/w3c/webcomponents/commit/1709f1242810a380bf641f85b67bb179e7ff39d8 I appreciate any feedback. Tab, could you remove the section, "3.3.2. Inheritance", from the css-scoping if you are comfortable with this?
I've filed a bug for CSS Scoping. https://www.w3.org/Bugs/Public/show_bug.cgi?id=28492 Let me close the bug in Shadow DOM side.