Re: [csswg-drafts] [css-grid-1] Behavior of an item spanning several auto minimum tracks (#9075)

The CSS Working Group just discussed `[css-grid-1] Behavior of an item spanning several auto minimum tracks`, and agreed to the following:

* `RESOLVED: close no change and add tests`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> TabAtkins: Go look at the code issue for an example to make this sensible<br>
&lt;fantasai> live example: issue<br>
&lt;fantasai> https://jsfiddle.net/4edu3v7z/1/<br>
&lt;fantasai> s/issue//<br>
&lt;bramus> … cor here is if you have an item spanning auto mulitple tracks. we believe tha tchrome behavior has not updated to latest spec<br>
&lt;bramus> … in example here, every browser is basically wrong (have not tested safari)<br>
&lt;bramus> … in this example we got a grid item that is 20px min width and got a bunch of 25px floating children so its min content is 25px and its max content is 100px<br>
&lt;bramus> … crome ends up distrigibuting that 20px<br>
&lt;bramus> … firefox instead distributes the 25 evenly and the flaots correctly fill the grid<br>
&lt;bramus> … afaik firefox is correct and following the intention<br>
&lt;bramus> … and chrome is not doing the second paragraph of the step that handles the space distribution for this case<br>
&lt;astearns> https://usercontent.irccloud-cdn.com/file/qrtTBDuP/image.png<br>
&lt;bramus> … if you take htis example and remove widht 0 on body, chrome continues to do wrong thing. firefox does sth else weird but maybe because of a different but<br>
&lt;bramus> … our conclusion is spec is probably right, and browsers are wrong<br>
&lt;bramus> … if that is the case, then we can close the issue and the bugs need to be fixed<br>
&lt;bramus> iank_: this case is expliclitly testing the grid min size as min content<br>
&lt;bramus> TabAtkins: yeah, under a min-contnet or max content constraint. because grid is self (missed). you can trigger either behavior with width 0 on the body or (missed2)<br>
&lt;bramus> … if you follow link to spec, chrome’s behavior is explained by it only doing the first paragraph<br>
&lt;bramus> … i believe firefox does entire thing<br>
&lt;bramus> fantasai: and the max content bug in firefox seems to be related to next issue<br>
&lt;fantasai> fantasai: where the spec has a bug<br>
&lt;bramus> astearns: are the wpt for this?<br>
&lt;bramus> TabAtkins: not yet, needs to fixed as well<br>
&lt;bramus> astearns: unless reserverations, seems like we need to write wpt and file bugs for differences<br>
&lt;bramus> TabAtkins: yeah<br>
&lt;bramus> dholbert: looks like safari matches chrome<br>
&lt;bramus> iank_: (missed) complications?<br>
&lt;bramus> astearns: I expect that<br>
&lt;bramus> astearns: proposed resolution is to close no change but put wpt in place and file browser issues<br>
&lt;bramus> RESOLVED: close no change and add tests<br>
</details>


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


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

Received on Tuesday, 18 July 2023 21:54:22 UTC