- From: Alison Maher via GitHub <noreply@w3.org>
- Date: Thu, 18 Sep 2025 18:16:59 +0000
- To: public-css-archive@w3.org
I took another look into this, and that could make sense. Currently, according to the [spec](https://drafts.csswg.org/css-grid-2/#algo-single-span-items), "If the track has an [auto](https://drafts.csswg.org/css-grid-2/#valdef-grid-template-columns-auto) [min track sizing function](https://drafts.csswg.org/css-grid-2/#min-track-sizing-function) and the [grid container](https://drafts.csswg.org/css-grid-2/#grid-container) is [NOT] being sized under a [min-](https://www.w3.org/TR/css-sizing-3/#min-content-constraint)/[max-content constraint](https://www.w3.org/TR/css-sizing-3/#max-content-constraint)...set the track’s [base size](https://drafts.csswg.org/css-grid-2/#base-size) to the maximum of its items’ [minimum contributions](https://drafts.csswg.org/css-grid-2/#minimum-contribution), floored at zero." `repeat(auto-fill, minmax(auto, auto))` currently falls into this case, and sets the base size based on the min content. And because we don't maximize tracks when determining the number of repeats here, we end up with a base size of 0, which results in the behavior in this issue. Will we need to update https://drafts.csswg.org/css-grid-2/#algo-single-span-items to use the max in this case, instead? -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12563#issuecomment-3308947109 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 September 2025 18:16:59 UTC