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

The CSS Working Group just discussed `[css-cascade-6] The specificity of a scope rule`, and agreed to the following:

* `RESOLVED: the specificity of the scope root is not applied to selectors from scoped rules`

<details><summary>The full IRC log of that discussion</summary>
&lt;fremy> miriam: in the current spec, the specificity of scope works very much like nesting<br>
&lt;fremy> miriam: in that the scope selector gives its specificity to all selectors inside<br>
&lt;fremy> miriam: this seems split 50/50 between people<br>
&lt;fremy> miriam: but this sounds like an accidental side effect that is not necessary<br>
&lt;fremy> miriam: so, we should probably not apply it<br>
&lt;TabAtkins> +1<br>
&lt;bramus> q+<br>
&lt;fantasai> +1<br>
&lt;ydaniv> +1<br>
&lt;fremy> +1<br>
&lt;astearns> ack bramus<br>
&lt;TabAtkins> the thread definintely didn't seem 50/50, but it might be more evenly split in general ^_^<br>
&lt;fremy> bramus: in the thread, I added some doubts, but in the end I agree<br>
&lt;fremy> fantasai: and if you want the other behavior, you can use ampersand<br>
&lt;fremy> miriam: yes, ampersand would work<br>
&lt;fremy> astearns: easier than designing an opt-out<br>
&lt;fremy> astearns: ok, can we get a short summary of the resolution?<br>
&lt;fremy> miriam: the specificity of the scope root is not applied to selectors from scoped rules<br>
&lt;fremy> astearns: any objection?<br>
&lt;fremy> RESOLVED: the specificity of the scope root is not applied to selectors from scoped rules<br>
</details>


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


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

Received on Wednesday, 1 March 2023 17:28:10 UTC