Re: [csswg-drafts] [css-cascade-6] Should the scope proximity calculation be impacted by nesting scopes? (#10795)

> But at that point we're just re-creating a more blunt form of specificity, right?

Hm, there is a divergence, though? As in, more specific scope selectors don't necessarily equate to "more deeply nested?" e.g.  `@scope (.foo.bar.baz) { .target { /*...*/ } }` versus `@scope(.a) { @scope (.b) { .target { /*...*/ } } }`

Also, we're firmly in the realm of edge cases, but if there's an implicit selector in the nesting, what's the proposed specificity? e.g. `@scope (.a) { @scope (.b) { @scope { .target { /*...*/ } } } }`



-- 
GitHub Notification of comment by dshin-moz
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10795#issuecomment-2436204058 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 24 October 2024 19:40:55 UTC