- From: Miriam Suzanne via GitHub <noreply@w3.org>
- Date: Thu, 13 Nov 2025 17:50:24 +0000
- To: public-css-archive@w3.org
First, `100px` is very small for most real-world examples. More likely we're repeating something in `15em`-`25em` range where the `em` is regularly larger than `16px`. But even with only a `< 100px`, designers care about filling that space well. But you're right that it's not common to use intrinsic sizes here, and the common repeater is already something like `repeat(auto-fit, minmax(min(20em, 100%), 1fr)` (where the min helps avoid overflow on small screens). I don't think I've seen much use of intrinsic sizing in repeaters. But it seems like you think of `minmax()` as similar to `max()` where adding a value in the `min` side clamps the value on the `max` side. I think of it a bit differently: `minmax()` is the range of acceptable sizes for my columns. So if I say I want repeating `minmax(100px, min-content)`, then I want columns that _start at `100px` and grow up to `min-content`_. In order to get that result, columns should be added at the `min` value and expand up to the `max`. If I want `min-content` clamped above `100px`, I don't expect to reach for `minmax()` – I expect `max()` to be the better clamping function. And so I would look for a way to do it with `calc-size()` (and then feel sad about the lack of browser support). I see that's not how `minmax(100px, 200px)` works, and I find it confusing. What's even the point of the min value if we never use it? In order for the min to matter, it has to be used for calculating the track count. Which is why I don't think I've ever seen a repeater using definite lengths on both sides of `minmax()`. I have no idea what use-case that would even address. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12573#issuecomment-3529002306 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 November 2025 17:50:25 UTC