- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Jan 2023 22:15:01 +0000
- To: public-css-archive@w3.org
@romainmenke my understanding was that we had [decided to make `&` valid everywhere](https://github.com/w3c/csswg-drafts/issues/5745#issuecomment-1276466934). According to the [Editor's Draft](https://drafts.csswg.org/css-nesting/#nest-selector): > When used in the selector of a nested style rule, the nesting selector represents the elements matched by the parent rule. When used in any other context, it represents the same elements as :scope in that context (unless otherwise defined). I suppose it's not clear to me if you're allowed to leave the `&` off those selectors, when not in a nested style rule? Maybe that needs to be clarified? At the very least, all your example selectors seem to be allowed if you start them with `&`, which is normally implied by a relative selector. > One thing that might seem a bit weird in this scenario is that there’s only one pseudo available to select the start boundary, not one to select the lower boundary. Miriam had arguments that this wasn’t too big of a problem. @bramus Yeah, that might be a little odd, and may point to a `:boundary` selector being useful (name TBD of course). -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8377#issuecomment-1409433264 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 January 2023 22:15:02 UTC