- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Feb 2021 09:30:28 +0000
- To: public-css-archive@w3.org
A definite +1 to a math function, in the sense that it's evaluated at the same time and way `calc()` - that way I'd expect it to be very easy to implement. I'm wondering if it's necessary to limit arguments 2 & 3 to math-type values? Clearly that's how it will be used most of the time - really all the comments but https://github.com/w3c/csswg-drafts/issues/5009#issuecomment-625562169 are considering this general issue for lengths or numbers. Math functions can already be integers, lengths, angles etc, and if the type is invalid where used, the function itself is invalid. I realise it might mean changes, but I can't see any reason why extending that to strings and colors, for example, would be impossible. I'm not entirely convinced it would be useful, but that's to be determined. Trying to imagine some cases where wider types would be used, but the only ones I can come up with are pretty contrived: ```css #phone-number { background-color: if(9ch > 200px, #F00, #FFF); } .greeked { font-family: if(1em < 6px, "greeked", "sans-serif"); } ``` Although I have a sense of foreboding about that last one as it would change the values for "ex", possibly leading to a loop. Maybe I'm talking myself out of this, but still worth considering before they're ruled out. (and if this the bit where we bikeshed names then I'd opt for `if(5em<200px, 2em, 1em)` over `cond()`) -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5009#issuecomment-785753494 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 February 2021 09:30:30 UTC