[css-cascade] @scope as a nested grouping rule and CSSNestingDeclarations about csswg-drafts

[mirisuzanne]

Keeping scope consistent, I think we would use :where(:scope) {}, so the resulting specificity is 0,0,1. The only specificity comes from the div.

[andruud]

@mirisuzanne But the innermost rules would get 0,0,0 if we use :where(:scope){}, not 0,0,1. The innermost rules do not "see" the outer div rule. The thing that maintains a connection between div and the innermost rules is the intermediate <scope-start> selector, which gets an implicit & prepended. Inner :scope selectors then match the scoping roots created by that <scope-start>.

[mirisuzanne]

oh, you're right - the result is more like :where(div #foo) rather than div :where(#foo).

Huh, we should likely discuss these two issues together in the group. I think the logic makes good sense at every point along the way, but the zero-specificity result for bare declarations is still a bit surprising. Maybe a fine and reasonable result? But something we should clearly state, and demonstrate in examples.

[mirisuzanne]

Agenda+ to discuss along with #10389 and #9621