- From: Miriam Suzanne via GitHub <noreply@w3.org>
- Date: Wed, 03 Dec 2025 17:11:13 +0000
- To: public-css-archive@w3.org
The example of `minmax(100px, min-content)` relies on the assumption that an author _wants_ `min-content`-sized columns, but no column less than `100px`. Which is believable that someone might want that. But it doesn't seem any more likely than writing e.g. `minmax(100px, max-content)` and wanting the reverse – columns that start at `100px` and grow up to (but not past) `max-content`. The latter is a behavior you can already achieve in grid, and there's no particular reason it shouldn't work the same in `grid-lanes` besides "we _can_ do something else". What strikes me primarily is that authors think of `minmax()` as a way of saying it's ok for columns to be as small as one, and as large as the other. But when we default to the larger, we don't actually get that behavior. Instead… columns are just the large value, and the small value is ignored. Making grid-lanes lean even harder into that behavior seems backwards to me. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12573#issuecomment-3607902099 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 December 2025 17:11:14 UTC