[Bug 16317] [Shadow]: Clarify the meaning of /select/ and upper boundary encapsulation, styling

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16317

--- Comment #17 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #13)
> > I mean, multiple shadow case and nested shadow case.
> 
> I forgot to ask about whether /select/ rules in inert shadow dom subtrees
> should be applied or not.
> 
> Suppose that there exist the following DOM tree:
> 
> <host> ---- <sr1> ---- <sr2> ----- <sr3> ... --- <sr N>
>    |
>    +--child
> 
> and all shadow roots have <style> which has /select/ rules. But some of
> shadow roots have no <shadow>, i.e. inert shadow roots.
> 
> I think, this should work in the same mannar as @host @-rules. /select/
> rules in inert shadow roots should not be applied. Is this correct?

Can you explain why this matters? If the tree is inert, the fact that the rule
applies or not is not possible to detect -- right?

> 
> And I think,/select/ rules in younger shadow DOM subtree should have higher
> priority than rules in older shadow DOM subtree.

You mean specificity?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.