- From: Mike Mai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Sep 2021 20:17:04 +0000
- To: public-css-archive@w3.org
> The reasoning for using `@when` over `@if` is that `@if` clashes with Sass, a widely used CSS preprocessor. No other reasoning exists for this decision. Since this thread leads with that, I'll re-iterate my thoughts from elsewhere: > From a standards and conventions point of view, I think that (choose `@when` over `@if`) sets a bad precedent. It will lead to other makers of 3rd party tools to think "well, if we are popular enough, the CSS spec will just design around us". I know Sass isn't just an ordinary 3rd party tool, so it's even more important for them to lead by example. Breaking changes are hard to deal with, but whoever chooses to use a third party tool has the responsibility to adapt changes. I know some have expressed that `@when` is actually a better choice because it describes what it does, but I am failing to see any examples making a convincing case. Please share some actual code examples (intended usage) for those who don't have the context. -- GitHub Notification of comment by mikemai2awesome Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-926895401 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 September 2021 20:17:07 UTC