- From: Ibby Wedin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Sep 2022 05:55:45 +0000
- To: public-css-archive@w3.org
The `@custom-selector` spec, such as it is, is also part of a truly bonkers [editor's draft](https://drafts.csswg.org/css-extensions/#custom-selectors); we're deep in the realm of hypothetical here, and there is general interest is introducing some scope control when nesting (#6809, #6330).
In this case, though, that detail just makes things a nice to use without having to resort to shadow DOM shenanigans. You could just as easily define `:--granny` in the global scope:
```
@custom-selector :--granny .a
--granny {
& .b {
@nest --granny:not(.c) &
}
}
```
--
GitHub Notification of comment by WCWedin
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6977#issuecomment-1244935137 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 September 2022 05:55:47 UTC