Re: [csswg-drafts] [css-values] Make min and max value optional in `clamp()` (#9713)

The fact is still that max()/min() can be confusing to use, depending on what you're going for. If your intention is "use the largest of these two values", then max() is exactly what you need and completely intuitive. If your intuition is "use this value, but clamp it to a maximum of this second value", then the fact that you have to use *min()* for that is easy to get confused about. People *regularly* write that using max(), in my experience, and then are confused why that doesn't work.

So for the "use this value, but clamped above/below by this second value", using clamp() with only one bound makes a lot more sense.

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


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

Received on Wednesday, 24 January 2024 18:00:53 UTC