- From: Evgeny Vrublevsky via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Nov 2021 18:17:22 +0000
- To: public-css-archive@w3.org
It looks like the people who voted for additional level of indentation just didn't use nesting in SCSS and don't know how deep it can be. It is always better to avoid too much of indentation if there are no good reasons for it. > <dholbert> TabAtkins: there are certain selectors you can construct that look like property declarations > <dholbert> TabAtkins: requires too much lookahead for UAs to implement that I don't get it. This new feature will be used everywhere in a few years after it is available in all modern browsers. It is really a new major feature in CSS. And browser developers don't want to update their parsers to make the most convenient syntax possible? It is not that hard to implement look ahead to check if it looks like a property or not. It is worth to spend some time to implement it. It is quite an important thing, and it will be used by millions of developers. If it not feasible, the solution with `@nest` before every rule is much better. One day in the future, browser developers probably will be willing to update their CSS parsers to support the most convenient SCSS-like syntax. All that would be required in this case is to allow implicit `@nest` for all cases, no any other changes in syntax. Oh... Just dreaming. -- GitHub Notification of comment by vrubleg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-962114604 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 November 2021 18:17:23 UTC