- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Jun 2013 21:35:18 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22390 Steve Orvell <sorvell@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sorvell@chromium.org --- Comment #4 from Steve Orvell <sorvell@chromium.org> --- In the f2f on this last Friday, we decided that :host should *not* allow combinators, as Tab noted. The idea is that from a given shadowRoot, it's important to be able to glean some information about the composed tree (for example, does it match an important theming selector), but it's brittle to rely on composed tree structure (is A inside of B) because its details may change and shouldn't be known to a given shadowRoot. Hayato-san, in your document, it looks like you're proposing that :host allow combinators as long as they match within the host scope. That's an interesting restriction and addresses the concern above, but my sense is that the additional expressiveness is offset by the arcane host scope matching behavior. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 June 2013 21:35:19 UTC