- From: Matthew Dean via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Mar 2022 14:12:31 +0000
- To: public-css-archive@w3.org
@LeaVerou I agree. It actually feels less, er, scripty? Than `@if` / `@when`? And what I've seen so far just embeds new `supports()` or `media()` functions, so I'm not understanding why `@if` and `@when` are even needed. You can't define global variables in CSS yet, which is the typical use case for `@if` in Sass (and the same `when` guard construct in Less), so why not just do `@supports` / `@else` and `@media` / `@else` if that's all CSS wants to use an `@if` / `@when` for? 🤔 Seems like there could be two proposals: one initial one just for `@else`. Then later, decide if anything else (ha) is needed (like if CSS adds global / stylesheet variables). -- GitHub Notification of comment by matthew-dean Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/112#issuecomment-1076423634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 March 2022 14:12:33 UTC