Re: [csswg-drafts] [css-cascade-6] `&` matching inside the `@scope`, and its interaction with `:scope` (#9740)

The CSS Working Group just discussed ``[css-cascade-6] `&` matching inside the `@scope`, and its interaction with `:scope` ``.

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> miriam: we discussed tis in the scope breakout session<br>
&lt;kbabbitt> ... idea is changing exactly what &amp; refers to when directly inside a scope rule<br>
&lt;TabAtkins> +1 to this resolution, based on reading Miriam's post summarizing the decision<br>
&lt;kbabbitt> ... goal is to match how &amp; works elsewhere<br>
&lt;kbabbitt> ... thinking about it slightly differently than before<br>
&lt;kbabbitt> ... existing spec says &amp; directly inside scope refers to selector in scope prelude<br>
&lt;kbabbitt> ... would get its specificity and match any elements taht target that selector<br>
&lt;kbabbitt> ... but that feels different from how &amp; works in other context<br>
&lt;kbabbitt> ... it would match exactly the same things it would match with bare declarations in that same place<br>
&lt;kbabbitt> ... so adding &amp; doesn't change what's matched and doesn't change specificity<br>
&lt;kbabbitt> ... proposal here is to say, in order to get that same behavior in a scope rule, bare declarations match :where scope which has 0 specificity and only matches single scope root element<br>
&lt;kbabbitt> ... &amp; should do the same thing in that context<br>
&lt;kbabbitt> ... match where scope, maintain 0 specificity, match only scope root<br>
&lt;kbabbitt> astearns: you wrote an excellent blog post going through this which definitely helped me<br>
&lt;kbabbitt> astearns: questions? concerns?<br>
&lt;TabAtkins> https://css.oddbird.net/scope/parent-selector/<br>
&lt;kbabbitt> astearns: purpose of bringing this back to agenda is to validate what we resolved on breakout<br>
&lt;kbabbitt> ... if there are no concerns we'll have resolution stand<br>
&lt;JoshT> +1<br>
&lt;lea> +1 to this<br>
&lt;kbabbitt> [no concerns raised]<br>
&lt;ydaniv> +1<br>
</details>


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


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

Received on Wednesday, 16 July 2025 16:07:17 UTC