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

The CSS Working Group just discussed `Distribute extra space into non-intrinsic tracks instead of going beyond growth limits`, and agreed to the following:

* `RESOLVED: When calculating content based base sizes of spanning items, if extra space needs to be distributed past the growth limit, and there is a range available in another column, put it in there`

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: Distribute extra space into non-intrinsic tracks instead of going beyond growth limits<br>
&lt;heycam> github: https://github.com/w3c/csswg-drafts/issues/3648<br>
&lt;heycam> fantasai: let's say there are two columsn<br>
&lt;heycam> ... one is minmax(0, 100px), the other is minmax(auto, 100px)<br>
&lt;heycam> ... normally we do a first pass to figure out hte base size<br>
&lt;heycam> ... min size of each column<br>
&lt;heycam> ... first is fixed and gets 0<br>
&lt;heycam> ... the seoncd is roughlty hte min content contribution of any items in that column<br>
&lt;heycam> ... let's support that item is 150px<br>
&lt;heycam> ... the max specified here is 100px<br>
&lt;heycam> ... since the first column says I'm 0px, we put all 100 or 150px into the second column<br>
&lt;heycam> ... and blow out the maximum<br>
&lt;heycam> ... in order to fit the content<br>
&lt;heycam> ... but the author did give us some space, first column has a range<br>
&lt;heycam> ... instead of blowing out the max on the second column, we could take those 50px and put them into the first column<br>
&lt;heycam> ... and it wouldn't violate any of the max constraints on the columns<br>
&lt;heycam> ... we ran this idea by jensimmons_ and rachelandrew_ and they both said yeah we'd expect that to happen<br>
&lt;heycam> ... so I'm suggesting adjusting the grid alg so that when computing hte min size of a spanning item, if you hit the growth limit, and have another that is still be low its max, you increase that one<br>
&lt;heycam> TabAtkins: sounds reasonable<br>
&lt;heycam> rachelandrew_: I like this because it is more similar to the flex behavior, which people will expect<br>
&lt;heycam> ... why overflow the column when there is still space there<br>
&lt;heycam> ... this could happen when you have a single row grid, and they're using grid for whatever reason, and they'll expect that space to be used<br>
&lt;heycam> iank_: what happens if the item is 150px in width?  are the columns 50px and 100px?<br>
&lt;heycam> fantasai: yes<br>
&lt;heycam> jensimmons_: right now they're 0 and 150 but we're proposing they be 50 and 100<br>
&lt;heycam> Rossen: any objections?<br>
&lt;heycam> RESOLVED: When calculating content based base sizes of spanning items, if extra space needs to be distributed past the growth limit, and there is a range available in another column, put it in there<br>
&lt;heycam> iank_: you'll need to specify which columns take the slack<br>
&lt;heycam> ... 2 on the left and 2 on the right<br>
&lt;heycam> fantasai: all of them<br>
</details>


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

Received on Thursday, 28 February 2019 01:27:06 UTC