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?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> Topic: [css-flexbox] Change content-size suggestion to min-intrinsic instead of min-content?<br>
&lt;emeyer> github: https://github.com/w3c/csswg-drafts/issues/6794<br>
&lt;emeyer> fantasai: I think I need to go back to read the flexbox specs from the very beginning to figure out what I think should happen here.<br>
&lt;emeyer> …I think we have to decide what behavior we want here and how to achieve that.<br>
&lt;emeyer> …I’m not sure I’m clear on any of that.<br>
&lt;emeyer> TabAtkins: Same here.  This is important and VERY difficult to reason about correctly, and we need more time.<br>
&lt;emeyer> dgrogan: Base issue is that aspect-ratio define sizing one way and flex defines it another<br>
&lt;emeyer> …and they conflict when you aspect-ratio a flex item.<br>
&lt;emeyer> TabAtkins: That’s what I understand.  I don’t know how to resolve that yet.<br>
&lt;emeyer> dgrogan: Before we start talking about changing the spec, should I change Chrome to match Firefox where they apply both minimums?<br>
&lt;emeyer> TabAtkins: Wouldn’t that answer the question?<br>
&lt;emeyer> …Because if you change to match Firefox, then the spec will just match whetever you do.<br>
&lt;emeyer> dgrogan: Okay, let’s pinch this off now.<br>
&lt;emeyer> astearns: Will remove Agenda+ and will put it back once fantasai and tabatkins have time.<br>
&lt;emeyer> iank_: Can we do this quickly?  It’s a major problem.<br>
&lt;emeyer> TabAtkins: That’s the goal.<br>
&lt;emeyer> astearns: Let’s wait on this for now.<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-1022434789 using your GitHub account


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

Received on Wednesday, 26 January 2022 17:40:33 UTC