Re: [csswg-drafts] [css-grid] Inconsitence of the "intrinsically-sized track" concept when using flexible tracks

> This is the main doubt that I, and a few other devs at Igalia (we used several meetings to discuss about this and I admit we still haven't reach an agreement). Is the available space definite during the step 4 ? Can/Should assume that the rows' size determined in Step 2 can be used to set the grid container's height, hence it can/should we use it as definite available space for computing rows' size in Step 4 ?

Regarding this we're currently assuming in Chromium and WebKit that grid size (width and height) is definite when we repeat the track sizing algorithm (steps 3 and 4).
And @MatsPalmgren requested to add this in [a comment on a different issue](https://github.com/w3c/csswg-drafts/issues/1921#issuecomment-399170288):
> And that the grid container's block-axis size is definite and final after the first pass (so that it works similar to the inline-axis).


About the particular problem of this issue, I agree with @fantasai that we should determine this at the beginning and then don't change the status during the whole track sizing algorithm.

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

Received on Thursday, 20 September 2018 11:41:48 UTC