Re: [csswg-drafts] [css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content? (#6794)

The CSS Working Group just discussed `[css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content?`, and agreed to the following:

* `RESOLVED: change minimum size of flex items to be the larger of min-intrinsic and transferred size`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> iank_: this is re auto min size on flex items and aspect-ratio<br>
&lt;emilio> ... blink is more or less consistently dropping the aspect-ratio<br>
&lt;emilio> ... other browsers are sometimes dropping it<br>
&lt;emilio> ... blink has been on the receiving end of a bunch of web dev bug reports<br>
&lt;emilio> ... this situation isn't good for web devs<br>
&lt;emilio> ... haven't seem bug reports for the other engines<br>
&lt;emilio> ... as such I think we would do a change to respect aspect-ratio<br>
&lt;emilio> ... we can add a bunch of tentative tests about this behavior<br>
&lt;emilio> ... proposal would be max(aspect-ratio, min-intrinsic size)<br>
&lt;TabAtkins> I'm happy to take the change, I'll just have to spend some time digesting exactly what it is. But if we're getting compat issues and webdevs are preferring one behavior, let's do it.<br>
&lt;dholbert> s/aspect-ratio/transferred-size/<br>
&lt;dholbert> (in the min() expression)<br>
&lt;dholbert> (er max() expression)<br>
&lt;emilio> fantasai: I'd like to<br>
&lt;fantasai> s/I'd like to/I'm the same as Tab here/<br>
&lt;emilio> ... TabAtkins and I would like to spend some time on this issue, but if there are compat issues...<br>
&lt;emilio> iank_: Yeah I'm going to try changing blink and add tests<br>
&lt;emilio> fantasai: I think I understand the proposal now<br>
&lt;emilio> ... I think it makes sense?<br>
&lt;chrishtr> +1 to accepting the change<br>
&lt;emilio> astearns: should we resolve on accepting this change tentatively?<br>
&lt;emilio> q+<br>
&lt;astearns> ack emilio<br>
&lt;emilio> iank_: what's going on is web devs really hate it when the aspect-ratio gets dropped<br>
&lt;emilio> q+<br>
&lt;emilio> iank_: I think proposed resolution would be to change the AMS of flex items to be max(min-intrinsic-size, transferred-size via aspect-ratio)<br>
&lt;astearns> ack emilio<br>
&lt;fantasai> fantasai: ok, got it<br>
&lt;fantasai> emilio: Do we understand what Gecko and WebKit are doing?<br>
&lt;fantasai> iank_: I understand, it's complicated<br>
&lt;fantasai> iank_: WebKit and Gecko are inconsistent between row/column axes, and aren't consistent in when transferred size is applied.<br>
&lt;emilio> they are inconsistent between column / row and how the transferred size is getting applied<br>
&lt;fantasai> iank_: everyone is super inconsistent<br>
&lt;fantasai> emilio: if you could write it up, I'd be curious<br>
&lt;fantasai> iank_: my intention was to write out a suite of testcases for this behavior<br>
&lt;fantasai> iank_: that should show what's happening<br>
&lt;fantasai> iank_: issue is that Web devs are running into behavior where WEbkit/Gecko are consistent in honoring aspect ratio and Blink isn't<br>
&lt;fantasai> emilio: so your proposal would be breaking changes for all three engines<br>
&lt;fantasai> emilio: right?<br>
&lt;fantasai> iank_: yes, because we're all inconsistent. And inconsistent across axes. Basically everyone is bad.<br>
&lt;fantasai> iank_: we're probalby the most consistent, but not what web devs expect<br>
&lt;fantasai> iank_: so that's where we are<br>
&lt;fantasai> emilio: ok, this sounds good. We'll look at tests. On paper sounds reasonable.<br>
&lt;fantasai> iank_: given lack of bug reports on other engines, not worried<br>
&lt;fantasai> astearns: Proposed resolution to change minimum size of flex to be the larger of min-intrinsic and transferred size<br>
&lt;emilio> PROPOSED: change the AMS of flex items to be max(min-intrinsic-size, transferred-size via aspect-ratio)<br>
&lt;emilio> RESOLVED: change minimum size of flex items to be the larger of min-intrinsic and transferred size<br>
</details>


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


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

Received on Wednesday, 22 May 2024 16:49:02 UTC