Re: [csswg-drafts] [css-values-5] we should ensure an if with no fallback can be reasoned about later (#10956)

@keithamus I don't understand the second example, I think there may be a typo there? The first one won't work with the current behavior, but that’s a bit of a special case (empty values are valid in custom properties). For non-custom properties, if their whole value is `if()` they would become IACVT if nothing matches. However, in the general case, an empty token stream is _more_ composable, as you can have multiple sequential `if()` that are independent and compose a value, whereas if a single `if()` makes the whole declaration IACVT, that limits what you can do.

I suspect your first example can be rewritten, but without a real-world use case it's hard to suggest how.

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


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

Received on Thursday, 26 September 2024 17:55:10 UTC