- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 Mar 2012 01:04:56 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16317 Summary: [Shadow]: Clarify the meaning of /select/ and upper boundary encapsulation, styling Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Component Model AssignedTo: dglazkov@chromium.org ReportedBy: dominicc@chromium.org QAContact: public-webapps-bugzilla@w3.org Blocks: 14978 Section 7.3 describes CSS selectors like: .some-insertion-point /select/ div.special where the left-hand side selects an insertion point and the right-hand side selects an element distributed to that point. Hence the left-hand side is in a shadow tree and the right-hand side is in a different level. However Section 5.1 states: The selectors must not cross the shadow boundary And the algorithm at the start of Section 7 describes rules in the document applying to nodes in the shadow tree if apply-author-styles is set, but not rules in the shadow tree applying to nodes in the document (ie styles flow at most "one way", if at all.) The intent of the /select/ combinator seems to be to style nodes in the document from rules in the document (by the algorithm in Section 7, rules in the shadow tree could not apply to nodes in the document.) However then the selector violates upper-boundary encapsulation by mentioning an insertion point in the shadow tree. This section is unclear and needs to be clarified. Is upper-boundary encapsulation relaxed? Are there exceptions for applying style rules that use the /select/ combinator? Is the combinator expected to work in querySelector as well as stylesheets? -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 12 March 2012 01:04:58 UTC