- From: <bugzilla@jessica.w3.org>
- Date: Wed, 17 Dec 2014 11:35:54 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27637
Bug ID: 27637
Summary: [Shadow]: Explain the CSS inheritance in terms of
ComposedTree
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: hayato@chromium.org
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
Blocks: 14978
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
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 17 December 2014 11:35:57 UTC