- From: Matthieu Dubet via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 13:59:44 +0000
- To: public-css-archive@w3.org
In this case, the selector list of the inner rule has an explicit `&`, thus it doesn't have the implicit `:scope`. (but it ends up being the same selector anyway) > Any selector in the [relative-selector-list](https://drafts.csswg.org/selectors-4/#typedef-relative-selector-list) that does not start with a [combinator](https://drafts.csswg.org/selectors-4/#selector-combinator) but does [contain the nesting selector](https://drafts.csswg.org/css-nesting-1/#contain-the-nesting-selector) or the [:scope](https://drafts.csswg.org/selectors-4/#scope-pseudo) selector, is interpreted as a non-[relative selector](https://drafts.csswg.org/selectors-4/#relative-selector) (but the [subject](https://drafts.csswg.org/selectors-4/#selector-subject) must still be [in scope](https://drafts.csswg.org/css-cascade-6/#in-scope) to match). -- GitHub Notification of comment by mdubet Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9370#issuecomment-1822827662 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 13:59:46 UTC