Re: [csswg-drafts] [css-cascade] Allow declarations directly in @scope? (#10389)

I think the main source of confusion here would be determining the specificity. Currently these have different specificities:

```css
@scope (#foo) {
  p { /* 0,0,1 */ }
  :scope p { /* 0,1,1 */ }
  & p { /* 1,0,1 */ }
}
```

That's already somewhat confusing, since `:scope p` and `p` have identical behavior. When you remove the nested `p` and consider `:scope` vs bare declarations (with implied-`:scope`), it should likely have the same specificity implications? `0,1,0` vs `0,0,0`?

I don't know if that causes round-trip issues when captured in CSSOM.

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


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

Received on Sunday, 9 June 2024 15:57:17 UTC