- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Feb 2023 19:19:37 +0000
- To: public-css-archive@w3.org
"contains the nesting selector" has that special text where we look for an & token *in the original tokens*, before potentially throwing anything out for invalidity, so `:is(:unknown(&), div)` still counts as containing the nesting selector regardless of whether the browser understands the `:unknown()` pseudo or not. (We can't tell that `:unknown()`'s argument is meant to be a selector, after all!) We'd need to apply the same logic to `:scope`. This is unrelated to anything about match semantics. ---- > But that maybe causes a problem for treating & like :scope in a scoped context. [As currently specced](https://drafts.csswg.org/css-nesting/#nesting-at-scope), `&` does indeed match all the elements matched by the scope-start selector, rather than something more specific that only matches the single element that happens to be the scoping root for a given element. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8377#issuecomment-1433594334 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 February 2023 19:19:39 UTC