- From: Brad Kemper via GitHub <sysbot+gh@w3.org>
- Date: Sat, 28 Oct 2023 18:09:47 +0000
- To: public-css-archive@w3.org
@tabatkins So, my understanding of your proposal is that you couldn't just use `@nest` in place of `&` (which would lead to a similar specificity checking explosion), because it could only be used by itself and not combined with other selectors on the same line. And this `@nest` would be implied in certain cases, such as with at-rules around bare declarations, or with declarations after at-rules. Do I have that right?
So it would help with this:
```
button, .button{
color: blue;
@media (...) { color: red; }
color: green;
}
```
But not with this:
```
button, .button {
span {
color: blue;
@media (...) {
i {
color: red;
}
}
color: green;
}
}
```
I'm curious where `@nest` would end up in the desugaring of that. I think I know, but I'm not sure.
--
GitHub Notification of comment by bradkemper
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9492#issuecomment-1783887584 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 28 October 2023 18:09:49 UTC