- From: <bugzilla@jessica.w3.org>
- Date: Mon, 20 May 2013 08:07:11 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21390 --- Comment #3 from Takashi Sakamoto <tasak@google.com> --- Thank you for replying. (In reply to comment #2) > I'm not sure I follow this. Are you just saying that we're changing the > @host rule from always matching the host element to matching other elements? > If so, then yes, that's the goal of adding ::shadow, to be able to style > shadowDOM elements based on the host's selectors. I just confirm ::shadow's situation. When we write something like "div:not(...)", we want to get "div" (:not(...) is just specifying div's condition. So "..." part is just a sub-selector). div::shadow(...) is different from the above. We don't want to get "div". We need to look into "..." part from "div". > Yes, the above rules (first set) don't make sense. I vote to disallow that. That makes sense. I would like to ask one more. I found another concerns, i.e. multiple pseudo elements. @host { // unknown pseudo + ::shadow .bar::x-unknown-pseudo::shadow(.foo) { ... } // multiple ::shadow .bar::shadow(.foo)::shadow(.foobar) { ... } // ::shadow + ::distributed .bar::shadow(.foobar)::distributed(.foo) { ... } } We should support all the above cases, support some of the above or disallow all the above? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 20 May 2013 08:07:13 UTC