Re: [csswg-drafts] [css-cascade-6] Strong vs weak scoping proximity (#6790)

The CSS Working Group just discussed `[css-cascade-6] Strong vs weak scoping proximity`, and agreed to the following:

* `RESOLVED: cascade proximity is weaker than specificity`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> miriam: With @scope, there are two features that help avoid large scoped things overriding smaller scoped things<br>
&lt;emeyer> …ONe of those is pretty strong, which is the ability to set lower boundaries<br>
&lt;emeyer> …The other is somewhat weaker, which is a heuristic priority for inner over outer<br>
&lt;emeyer> …We’re calling that cascade proximity; question is whether that’s more or less powerful that the specificity heuristic<br>
&lt;emeyer> …Proposal is to have it be stronger than, because we’re trying to reduce specificity reliance<br>
&lt;emeyer> …When these two heuristics conflict, specificity is easier to change<br>
&lt;emeyer> s/stronger than/weaker than/<br>
&lt;emeyer> astearns: I suggested people provide arguments in favor of stronger, but all the comments in the issue argue for weaker<br>
&lt;emeyer> astearns: Comments?<br>
&lt;bramus> SGTM<br>
&lt;emeyer> RESOLVED: cascade proximity is weaker than specificity<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1479754855 using your GitHub account


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

Received on Wednesday, 22 March 2023 15:13:06 UTC