- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Aug 2022 17:15:22 +0000
- To: public-css-archive@w3.org
Didn't see it come up in the minutes but I think the results of any poll directed at stylesheet authors will be biased when it comes to nesting. In this case they were given the choice between the syntax that they use today with [postcss-nesting](https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-nesting#readme) or two alternatives. They will always pick the one that they use today. If they were given the choice for sass-like nesting they would have picked that because it is still the mental model for nesting for the majority of authors. ----- _meaningless extra data points :_ It seems that there were some question about `&` vs `@nest` initially but mostly people seemed to find their way even without a single syntax for nesting. - https://github.com/csstools/postcss-nesting/issues/62 - https://github.com/csstools/postcss-nesting/issues/22 -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-1233207407 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 August 2022 17:15:23 UTC