- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 Jun 2012 20:05:19 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16519
--- Comment #6 from Dimitri Glazkov <dglazkov@chromium.org> 2012-06-15 20:05:19 UTC ---
(In reply to comment #5)
> > @host {
> > div { background-color: white; }
> > .warning { background-color: yellow; }
> > .important .warning { background-color: orange; }
> > }
>
> I like this.
One use case that I came across was the need to react to DOM tree of the host
element. For instance, there's a body.loading -> body.loaded transition that
commonly occurs to indicate that the document has arrived to some stable state.
The shadow DOM subtrees may want to know about this transition (for example,
the widgets on the page would change appearance reflecting arrival to a stable
state.
I see a developer expecting to do something like this in the shadow DOM
subtree:
body.loading :host div.foo { ... }
body.loaded :host div.foo { ... }
Where:
* "body.loading", "body.loaded", and ":host" are matched in the subtree of the
host element
* div.foo are matched in the shadow subtree.
Clearly, this is wrong. The subtree of host element could be another shadow DOM
subtree, which means that these selectors will not match.
Perhaps I should tackle this a separate issue.
--
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 Friday, 15 June 2012 20:05:22 UTC