Re: [csswg-drafts] [css-grid] Automatic Minimum Size for grid items should not min against content size

The CSS Working Group just discussed `Automatic Minimum Size for grid items should not min against content size`, and agreed to the following resolutions:

* `RESOLVED: is either it's defined size, content size, or transfer size`

<details><summary>The full IRC log of that discussion</summary>
&lt;dauwhe> topic: Automatic Minimum Size for grid items should not min against content size<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/1149<br>
&lt;dauwhe> TabAtkins: in flex we do to some effort to find minimum size<br>
&lt;dauwhe> ... if it's image we try to figure out what information is important<br>
&lt;dauwhe> ... this is useful because flex uses this to size the image<br>
&lt;dauwhe> ... grid uses the info to size the track, and then lets the image size to the track<br>
&lt;dauwhe> ... the big difference is say you have a specified size of 100px and intrinsic size is 50px<br>
&lt;dauwhe> ... we use 50px in flex<br>
&lt;dauwhe> ... grid doesn't have to worry about shrinking<br>
&lt;dauwhe> ... "So, we think the right fix is to just change Grid's automatic minimum size to be the specified size if it exists, else the transferred size if it exists, else the content size."<br>
&lt;dauwhe> ... this better matches author intent for automatic minimum sizing of images<br>
&lt;dauwhe> (tab draws on whiteboard)<br>
&lt;dauwhe> ... image is 50px<br>
&lt;dauwhe> ... put in grid container, set to 100px<br>
&lt;dauwhe> ... in flex, minimum value is 50, it's allowed to shrink to that<br>
&lt;dauwhe> ... in grid, we prefer to say let's stick with 100, 'cause the author said so<br>
&lt;dauwhe> ... and avoid risk of overflow<br>
&lt;dauwhe> Rossen: additional piece: if you open the test case<br>
&lt;dauwhe> https://test.csswg.org/suites/css-grid-1_dev/nightly-unstable/html/grid-minimum-size-grid-items-007.ht<br>
&lt;dauwhe> TabAtkins: sets itself to 100px, but grid width is 10 x 10<br>
&lt;dauwhe> ... if we went by previous algo, track would be 50px<br>
&lt;dauwhe> ... maintaining aspect ratio is important<br>
&lt;dauwhe> astearns: any other comments?<br>
&lt;dauwhe> Rossen: this one has height set<br>
&lt;dauwhe> ... current spec says minimum of instrinsic and transfer?<br>
&lt;dauwhe> fantasai: use specified if you have it, content if you don't<br>
&lt;dauwhe> TabAtkins: edge does it<br>
&lt;dauwhe> ... any objections?<br>
&lt;dauwhe> astearns: hearing no objection,<br>
&lt;dauwhe> RESOLVED: is either it's defined size, content size, or transfer size<br>
&lt;dauwhe> (do what 1149 says)<br>
&lt;dauwhe> fantasai: there was one about stretching tracks<br>
</details>


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

Received on Friday, 4 August 2017 13:12:48 UTC