- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Mar 2022 23:50:13 +0000
- To: public-css-archive@w3.org
I am asking myself whether the name clash is an issue for Sass users or Sass developers. To me it sounds like it using a different syntax for `@if` is actually beneficial. It means that a future version of Sass could differenciate between its own and the CSS syntax and handle them differently. I.e. its own syntax will be compiled like it is now while the new CSS syntax will be part of the resulting CSS. For users, using the CSS syntax in a current version of Sass will result in a compile error (independently of whether it's called `@if` or `@when`). And that is fine. Once we settle on a syntax and Sass implements it, there won't be any compile errors anymore. The important point is that Sass needs to have support for the CSS syntax when (⇐ see, point in time, not condition 😉) the first browsers are shipping it to provide users with a way to transition to the new CSS syntax. Otherwise they may wonder why the syntax isn't working in Sass. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1064630704 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 March 2022 23:50:16 UTC