- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Oct 2021 18:53:53 +0000
- To: public-css-archive@w3.org
> You get to avoid writing a `@nest` keyword in front of each of your selectors, but in return you have to indent an extra level each time and deal with more matched braces. @tabatkins That seems like a really _good_ trade-off for not writing `@nest` in front of every selector, which is both a) annoying to type and b) uselessly noisy. I don't understand the resistance to another level of indentation. If your indents are too long, stop using 4 spaces. If you're not mixing in declarations you can also just double up your braces and indent one level. ``` outer {{ inner { something: foo; } more { other: foo; } }} ``` @LeaVerou I don't think I like that kind of statefulness, where what's parsed before as a sibling construct affects so fundamentally what's parsed after. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-932474932 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 October 2021 18:53:55 UTC