Re: [csswg-drafts] [css-flexbox] column wrap intrinsic size algorithm can make inline min-content > max-content (#6777)

The CSS Working Group just discussed `[css-flexbox] column wrap intrinsic size algorithm can make inline min-content > max-content`.

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> topic: [css-flexbox] column wrap intrinsic size algorithm can make inline min-content > max-content<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/6777<br>
&lt;emilio> dgrogan: so... background is that all engines have shipped the same intrinsic sizing algo for years<br>
&lt;emilio> ... but the algorithm is bad<br>
&lt;emilio> ... fantasai specified a new one in 2015 but nobody implemented it<br>
&lt;emilio> ... authors really want it<br>
&lt;emilio> ... but there's a big compat risk here<br>
&lt;emilio> ... but we want to ship it along everyone else so that authors just fix sites once<br>
&lt;emilio> ... we started implementing it and found this issue where min can be > max<br>
&lt;emilio> ... details are in the issue, there's a few possible things we can do<br>
&lt;emilio> ... one is flooring max to min<br>
&lt;emilio> ... or in this case making min the max content<br>
&lt;Rossen_> q?<br>
&lt;emilio> fantasai: I'm really excited you're working on this<br>
&lt;emilio> dgrogan: yeah authors really want this and current algorithm is bad<br>
&lt;emilio> TabAtkins: I see the problem, not sure what the best solution is but that's wrong<br>
&lt;emilio> ... fantasai and me will review asap<br>
&lt;emilio> iank_: we might testing the new thing in our canary channels and be more concrete about the compat risks<br>
&lt;emilio> ... we might have to go back for the old thing if we get tons of reports<br>
&lt;emilio> ... we might also want to do this incrementally, first for single-items flexboxes and so on<br>
&lt;fantasai> s/single-items/single-row/<br>
</details>


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


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

Received on Wednesday, 16 March 2022 17:01:32 UTC