- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Jan 2023 14:53:44 +0000
- To: public-css-archive@w3.org
So to sumarize : At this time it does not seem realistic to implement nesting in a way that is so close to nesting in preprocessors that it is indistinguishable for most users/projects. Preprocessors can change their implementation to match nesting as currently specified and deal with all the fallout from such a breaking change. This is a short term problem. But if authors agree that the resulting feature is less useful it means that implementing nesting in browsers has taken something away from authors instead of adding a new feature. This is a long term issue. Preprocessors could choose to keep their implementation and always desugar to unnested CSS. But this splits the ecosystem (dev tooling, learning resources,...). Leaving it as a preprocessors only feature might be better for authors? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8310#issuecomment-1387201169 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 January 2023 14:53:46 UTC