- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 16:07:16 +0000
- To: public-css-archive@w3.org
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> <kbabbitt> miriam: we discussed tis in the scope breakout session<br> <kbabbitt> ... idea is changing exactly what & refers to when directly inside a scope rule<br> <TabAtkins> +1 to this resolution, based on reading Miriam's post summarizing the decision<br> <kbabbitt> ... goal is to match how & works elsewhere<br> <kbabbitt> ... thinking about it slightly differently than before<br> <kbabbitt> ... existing spec says & directly inside scope refers to selector in scope prelude<br> <kbabbitt> ... would get its specificity and match any elements taht target that selector<br> <kbabbitt> ... but that feels different from how & works in other context<br> <kbabbitt> ... it would match exactly the same things it would match with bare declarations in that same place<br> <kbabbitt> ... so adding & doesn't change what's matched and doesn't change specificity<br> <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> <kbabbitt> ... & should do the same thing in that context<br> <kbabbitt> ... match where scope, maintain 0 specificity, match only scope root<br> <kbabbitt> astearns: you wrote an excellent blog post going through this which definitely helped me<br> <kbabbitt> astearns: questions? concerns?<br> <TabAtkins> https://css.oddbird.net/scope/parent-selector/<br> <kbabbitt> astearns: purpose of bringing this back to agenda is to validate what we resolved on breakout<br> <kbabbitt> ... if there are no concerns we'll have resolution stand<br> <JoshT> +1<br> <lea> +1 to this<br> <kbabbitt> [no concerns raised]<br> <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