- From: Sarah Drasner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Mar 2022 17:56:57 +0000
- To: public-css-archive@w3.org
I have massive respect for everyone in this thread, thank you for the thoughtful discussion so far. I support the `@when` or `@while` syntax and here is why: - **When/while make more sense as a mental model**. As @davidkpiano mentions [in this issue](https://github.com/w3ctag/design-principles/issues/335#issuecomment-922083819) and @matthew-dean mentions above, `when` makes more sense in a declarative stylesheet setting, `if` communicates parts of running code that would set other expectations, given common usages. If `@when` doesn't seem aligned enough with other programming languages, `@while`, proposed by [Amelia](https://twitter.com/AmeliasBrain/status/1504659144342753280?s=20&t=bQgm_4Mj-pexpzyJmnCZuA), would be a good compromise, as @mirisuzanne mentioned. Though it may break Sass, the usage isn't profound and the mental model of while conveys a continuous check. - **The breakage is non-trivial**. This impact not just Sass but also user space, as well as library author space for those who depend on Sass for tooling. I realize this is a complex problem, but I believe a path forward exists here where we take all requirements and restrictions account without major impacts to the ecosystem. Finally, as @mirisuzanne points out, let's please keep the discussion to the topic and not suggest how Sass should handle their work, @nex3 and team have been doing an amazing job maintaining Sass for many many years now, and it's not productive or helpful to give unsolicited advice on how to handle a breaking change, should that path be chosen. -- GitHub Notification of comment by sdras Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1075434684 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 March 2022 17:56:58 UTC