- From: Bramus via GitHub <noreply@w3.org>
- Date: Thu, 03 Jul 2025 08:30:48 +0000
- To: public-css-archive@w3.org
> https://blog.kizu.dev/scope-selector-nuance/ I don’t see the problem there, and think the stuff you described there is WAI. > PROPOSED: `&` in `@scope` behaves as `:where(:scope)`. This feels weird to me, as it’s deviating from what `&` does in nesting. --- One thing you could argue here instead, is whether using `@scope` should carve out a subtree based on `<scope-start>` and only consider that subtree in isolation when doing selector matching? Right now it doesn’t, but if it did then it would open up the door to possible performance gains for authors. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9740#issuecomment-3031368480 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 July 2025 08:30:49 UTC