Bug 1844184 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

This is about a case where a grid has `grid-template-columns: minmax(0, 100px) minmax(auto, 100px);`, i.e. it spans a track whose sizing function is fixed lengths (no intrinsic sizes) and a track whose sizing function depends on intrinsic sizes.  And with that setup, we've got a grid item that spans both tracks, which happens to be larger than 100px (say, 150px).

Previously we would expand the second track to 150px (blowing past its maximum).

This resolution says we should add an additional step, where we expand the second track up to its maximum, and then try to expand fixed-size tracks that haven't yet their maximum (up to their maximum), and then expand the second track beyond its maximum if necessary.
This is about a case where a grid has `grid-template-columns: minmax(0, 100px) minmax(auto, 100px);`, i.e. it spans a track whose sizing function is fixed lengths (no intrinsic sizes) and a track whose sizing function depends on intrinsic sizes.  And with that setup, we've got a grid item that spans both tracks, which happens to be larger than 100px (say, 150px).

Previously we would expand the second track to 150px (blowing past its maximum).

This resolution says we should add an additional step, so now we should expand the second track *up to* its maximum, and then (if necessary) switch to try to expand any spanned fixed-size tracks that haven't yet their maximum (and expand them up to their maximum if needed), and then go back to expanding the intrinsic size track (beyond its maximum if necessary, as we already do).

Back to Bug 1844184 Comment 1