Re: [csswg-drafts] [css-grid] minmax(auto,min-content) under a max-content constraint (#3565)

The CSS Working Group just discussed `[css-grid] minmax(auto,min-content) under a max-content constraint`, and agreed to the following:

* `RESOLVED: accept latest change`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> See https://github.com/w3c/csswg-drafts/issues/3565#issuecomment-1638901643<br>
&lt;bramus> TabAtkins: if you look at very first comment, oriol has a test case here with some example and the wg decided earlier that chrome and edge are correct here.<br>
&lt;bramus> … earlier we tried to implement that resolution in spec and we did it wrong, reverted, and did it again<br>
&lt;bramus> … issue ended up being simpler thatn we thought<br>
&lt;fantasai> Final fix was much simpler than we thought: https://github.com/w3c/csswg-drafts/commit/35ed93fc9296e6541e83c8cca4b705b7ba82c31a<br>
&lt;bramus> … we believe only problem was in handling non spanning items in a max content constraint was<br>
&lt;fantasai> s/max content/min content/<br>
&lt;bramus> … we were using the limitex max content size<br>
&lt;dholbert> s/limitex/limited/<br>
&lt;bramus> … we should have been using limited min content size when resolving base sizes of tracks<br>
&lt;bramus> … once we fixed that, algortihm made more sense in general<br>
&lt;fantasai> s/of tracks/of auto tracks/<br>
&lt;bramus> … this text also dated back to 2016 which was early in grid spec text, so we believe this was a mistake we made early on<br>
&lt;bramus> … this mistake was not copied over into spanning case but firefox behavior in previous issue was them doing the same thing in spanning case<br>
&lt;bramus> … if you do it in either case, it should be ok. we think spec text is ok now.<br>
&lt;bramus> astearns: you were nodding along?<br>
&lt;bramus> oriol: yeah, we discussed yeasterday and I think the current solution is the correct one<br>
&lt;bramus> astearns: other comments?<br>
&lt;bramus> astearns: proposed resolution to accept latest change as the solution to the earlier resolution<br>
&lt;bramus> astearns: objections?<br>
&lt;bramus> RESOLVED: accept latest change<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3565#issuecomment-1641048039 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:59:24 UTC