Re: [csswg-drafts] [css-cascade-6] `&` matching inside the `@scope`, and its interaction with `:scope` (#9740) from Romain Menke via GitHub on 2025-07-03 (public-css-archive@w3.org from July 2025)

From: Romain Menke via GitHub <noreply@w3.org>
Date: Thu, 03 Jul 2025 11:12:35 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-3031878595-1751541153-noreply@w3.org>

> 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. It would also bypass the whole `.outer :scope .inner` situation.

Does this make it impossible to have `.outer :scope .inner`  match anything?
Because that will take away a lot of utility, right?

Or do you suggest making the implicit case behave more like `.outer .inner:is(:scope *)`?


-- 
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9740#issuecomment-3031878595 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 11:12:36 UTC