- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Oct 2022 17:16:02 +0000
- To: public-css-archive@w3.org
If the goal is to do option 3 as an evolution of the current syntax, I think we should drop `@nest` entirely and just say "you can't do that in level 1, nested selectors just have to start with an ampersand". Otherwise we are stuck with `@nest` forever.
> In option 3 you also have to learn when and how to fix `.foo { bar & {} }` as I stated above : [#7834 (comment)](https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1283489362)
This is extremely rare however. I think it's fine to have weirdness in rare edge cases if it allows the common cases to have better DX.
--
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1284332552 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 October 2022 17:16:04 UTC