- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2022 21:50:10 +0000
- To: public-css-archive@w3.org
Yes the previous iteration of the nesting spec had `@nest` which allowed users to guard themselves against any and all issues by always writing `@nest`.
The linter rules needed to help authors write correct nested CSS have become more numerous and more complex with the new syntax.
I have added this example to the [list](https://github.com/stylelint/stylelint/issues/6421#issuecomment-1304286037).
> they don't need .foo anymore
Also a "simple" re-ordering of selectors.
```css
div {
textarea, .foo { … }
}
```
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7980#issuecomment-1304287748 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 November 2022 21:50:12 UTC