Re: [csswg-drafts] [css-cascade-6] The specificity of a scope rule (#8500)

Drawing a parallel with `@container` which also targets a certain parent element _(albeit by name)_ the specificity of the targeted boundary should not be taking into account and option 2 seems like the way to go.

But … that makes me doubtful of the position of `@scope` in the cascade _(strong vs weak)_. 

Say you have this:

```css
header a { /* (0,0,2) */
  color: hotpink;
}

@scope (nav) {
  a { /*(0,0,1) with Option 2*/
    color: lime;
  }
}
```

With weak scoping, links matching `header nav a` would be `hotpink` instead of `lime`, no? That might be pretty unexpected, I think.

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


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

Received on Tuesday, 28 February 2023 14:10:00 UTC