Re: [csswg-drafts] [css-values-5] What is the MVP for inline conditionals on custom properties? (#10064)

> Discussed it f2f with @tabatkins and @LeaVerou, they both are supporting required `else` for fallback approach. 

This is missing some important detail. The gist from our discussion with @tabatkins was that we were both ok with:
- `else` is mandatory IF you need a fallback
- If `else` is omitted, you get an empty token stream (which may or may not make the declaration IACVT depending on other values).

This largely alleviates my concern about verbosity, since the `else:` can still be omitted in a large number of cases, and you can still get the nice short `if(test? value)` syntax (separator TBB) and the composability of being able to easily specify empty token streams as the fallback. 

> So the only question remains 

Well, the fact that @tabatkins and I are in agreement doesn’t mean we don’t still need group consensus 😁 

> is preferable separators: `?:` vs `;` vs (`wrapper{}` or `,/,;` (upgradable commas) depends what we decide for the issue #9539).

I would say there are several syntax-level questions:
1. separator between condition and value-if-true (`?` vs `:`)
 - 1a: Is that different for the `else` clause?
3. I think we’re converging towards using regular argument syntax for the two values (as decided by #9539) rather than `:` (even if we use `?` for Q1.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2372435508 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 24 September 2024 21:38:23 UTC