- From: Kaelig Deloumeau-Prigent via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Mar 2022 18:27:10 +0000
- To: public-css-archive@w3.org
The debate is escalating in ways that seem unhealthy to me, and I even find more and more unpleasant to read. The CSS spec is full of quirks that were introduced with the best of intentions. We've learned and adapted our tooling along the way. It's _fine_. We all seem to agree that introducing `@if` in the CSS language would be a significant hinderance for the web dev community. So what's blocking us from doing something like this? ⬇️ 1. Concede that `@if` would be ideal, but here we are 🤷🏻 2. Use `@when`, as the best way to preserve interop with existing tooling 🤝 3. Document the decision, and publish guidance to prevent this from happening again (best practices for authors of pre-processors) 🖐🏻 4. Move on 🙏🏻 -- GitHub Notification of comment by kaelig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1072680249 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 March 2022 18:27:12 UTC