Re: [csswg-drafts] [css-grid] Distribute extra space into non-intrinsic tracks instead of going beyond growth limits (#3648)

OK, so we think the edits are in. However, there's this problem:

Suppose I have three tracks with `minmax(0, 10px)`, and 3px of available space. I put a 20px item into the first one. It doesn't care, because it only has fixed sizes. During Maximize Tracks, we distribute free space equally among all the tracks; 1px each.

Now suppose I make the 20px item span the first two tracks. Under the previous spec, none of the tracks care about this item. But under the new one, we distribute its space into the first two tracks, each getting 10px. Maximize Tracks then gives the third track 0 space.

* Under the previous spec, we would have three 1px tracks: the item would overflow its tracks, but the grid would not overflow its container, and the tracks that have fixed-size functions would be treated all equally.

* Under the new one, _only if the item spans multiple columns_, we take space for the item regardless of whether there is any free space, possibly overflowing the container in order to minimize items overflowing within the grid, and the equal fixed-size functions are not sized equally.

What do we actually want to do here? Some possible options that are at least consistent between spanning and non-spanning items:
* Fixed-size tracks completely ignore their content, as in the first edition.
* Fixed-size tracks prioritize accommodating content over equal distribution of free space, and may use up more space than the available free space, causing the grid to overflow its container.
* Fixed-size tracks prioritize accommodating content over equal distribution of free space, but cannot use up more than the available free space, and will allow the item to overflow before the grid itself overflows.



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


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

Received on Friday, 4 March 2022 00:38:11 UTC