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

The CSS Working Group just discussed `column wrap intrinsic size algorithm can make inline min-content > max-content`, and agreed to the following:

* `RESOLVED: Accept the proposal in the issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: column wrap intrinsic size algorithm can make inline min-content > max-content<br>
&lt;heycam> github: https://github.com/w3c/csswg-drafts/issues/6777<br>
&lt;heycam> dgrogan: this one is similar to the last one<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/6777<br>
&lt;fantasai> proposal: https://github.com/w3c/csswg-drafts/issues/6777#issuecomment-1220003107<br>
&lt;heycam> ... there have been spec proposal, but fantasai made a good proposal, implemented it not shipped, but it works well<br>
&lt;TabAtkins> summary at https://github.com/w3c/csswg-drafts/issues/6777#issuecomment-1220003107<br>
&lt;heycam> ... from calculating the min-content width of a column wrapped flexbox, instead of laying out all the items at their min-content width and then taking the result and calling that hte min-content width<br>
&lt;heycam> ... we'll just ignore wrapping<br>
&lt;heycam> ... so the min-content width of a column wrapped flexbox will be the same as a non-wrapped flexbox<br>
&lt;heycam> ... downside will be is there can be some overflow if the column wrapped flexbox has a definite height specified, such that the items need to wrap, but now they can't<br>
&lt;heycam> ... also point out this proposal is what all browsers implement today<br>
&lt;heycam> ... so it seems fine<br>
&lt;heycam> dholbert: seems fine to me<br>
&lt;heycam> fantasai: that's for min0content sizes<br>
&lt;heycam> ... guarantees even if you have overflow columns, the width of the box will be as wide as the widest column<br>
&lt;heycam> ... trickier is max-content size, where there's no real good answer<br>
&lt;heycam> ... proposal is to lay out each item at its max-content size, then try to build the columsn, then try to wrap a box around that set of columns<br>
&lt;heycam> ... mostly that should be a box that can size its contents exactly, but if the author used %age sizing there'd be cyclic effects<br>
&lt;heycam> s/min0content/min-content/<br>
&lt;heycam> dgrogan: what fantasai just proposed is already specced<br>
&lt;heycam> RESOLVED: Accept the proposal in the issue<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-1248752768 using your GitHub account


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

Received on Thursday, 15 September 2022 23:28:48 UTC