Re: [webcomponents] CSS Cascading Order in Shadow DOM should define behavior for closed shadow trees (#293)

In all cases, that's not problem what cascading order should handle. That's the problem what each selector should behave, isn't it?

> 1. Closed shadow tree has closed child shadow tree. Should we prevent cascading? Probably yes?
> 2. Closed shadow tree has open child shadow tree. Should we cascade? Probably yes?

I think we don't need to modify the proposal in either case. That's the problem about how a selector matches an element in a child tree.
- If it doesn't match, the cascading order doesn't matter.
- If it matches, the cascading order matters and the current rule is good enough, I think.

> 3. Closed shadow tree has open child shadow tree, and the child uses `:host`. Should this work, or prevented?

Yes. Note that it depends on the definition of ':host'. We don't need to modify the proposal.

> 4. A closed shadow tree has open child shadow tree, and the child shadow tree used `::content`, in which case the distributed content could be in a closed tree. I guess it should work?

Yes. Note that it depends on the definition of '::content'. We don't need to modify the proposal.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/293#issuecomment-130550761