- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Aug 2017 16:38:24 +0000
- To: public-css-archive@w3.org
Fixed max track sizes in the row axis are assumed at the beginning of the first column sizing pass, so the second interpretation can't happen in any case. Note the second paragraph: > First, the track sizing algorithm is used to resolve the sizes of the grid columns. > > If calculating the layout of a grid item in this step depends on the available space in the block axis, assume the available space that it would have if any row with a definite max track sizing function had that size and all other rows were infinite. A case where we could get this result would be if the grid container itself had a fixed height. A second comment is, if we're recalculating the column sizes, shouldn't the extra space from stretching be re-calculated? In which case we should still get the first result. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1150#issuecomment-319426378 using your GitHub account
Received on Tuesday, 1 August 2017 16:38:25 UTC