Re: [csswg-drafts] [css-flexbox] [css-sizing-4] Interaction of flexbox minimum height and aspect-ratio minimum height (#6069)

The CSS Working Group just discussed `[css-flexbox] [css-sizing-4] Interaction of flexbox minimum height and aspect-ratio minimum height`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-flexbox] [css-sizing-4] Interaction of flexbox minimum height and aspect-ratio minimum height<br>
&lt;dael> github:  https://github.com/w3c/csswg-drafts/issues/6069<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/6069#issuecomment-790046695<br>
&lt;dael> Rossen_: Summary ^<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/6069#issuecomment-797028657<br>
&lt;dael> Rossen_: Can you repeat it?<br>
&lt;dael> fantasai: Prop is a non-replaced element ignores transfered sizes for auto min sizing<br>
&lt;dael> fantasai: auto min siziing in flex and gri where initial value is auto. You take size of min-content so you don't shrink flex item too much. On images with aspect ratio if you set for row flexbox a height on the image we transfer that through a-r and modifies minimum<br>
&lt;dael> fantasai: Makes sense for images and that's what it was designed for. For non-replaced boxes this makes less sense. When we thought through we considered don't do this. Make this behavior restricted to replaced elements. Don't apply to non-replaced elements that have a-r added by a-r property<br>
&lt;Rossen_> q?<br>
&lt;dael> florian: You're left with min prior to a-r being used?<br>
&lt;dael> iank_: min-content or intrinsic<br>
&lt;dael> fantasai: For relaced element natural and min-content size is same.<br>
&lt;dael> fantasai: For repalced if you spec a size on the axis we clamp auto-min by that size.<br>
&lt;dael> fantasai: Other than that we transfer that and other conent and min that.<br>
&lt;dael> fantasai: Non-replaced we don't transfer<br>
&lt;dael> florian: If the transfer a-r would have made min size smaller clearly good to not do. If tranfer a-r makes min-size bigger is it not good to honor it?<br>
&lt;dael> fantasai: Trying to remember the logic<br>
&lt;dael> fantasai: This was because on items with an a-r...consider a block with a-r. min-height: auto. Decided that means element with an a-r will ignore a-r if content is larger than height it would have imposed by a-r. 1:1 a-r block. 100px width which gives 100h. 500px content so I have to block 500px<br>
&lt;dael> fantasai: When you turn it into a column flexbox we want same. But if we transfer size we can't get same behavior b/c made auto-min dictated by a-r. To have same behavior of the content blowing out the a-r in both blocks we can't use same transfer behavior we have for replaced<br>
&lt;dael> florian: Makes sense, thank you<br>
&lt;dael> fantasai: More like thanks cbiesinger<br>
&lt;dael> iank_: This means a min-content size will ignore tranferred min and max heights. But min-content contribution will respect them?<br>
&lt;dael> fantasai: min-content contribution will have to take into account...[thinks]...something complicated about this but I don't remember<br>
&lt;dael> fantasai: I think min-content contribution needs to take it into account. I remember complixity on how defined in a different issue and I'm not sure if it was relevent there<br>
&lt;dael> cbiesinger: min-content contribution doesn't matter?<br>
&lt;cbiesinger> s/?/in flexbox?/<br>
&lt;dael> cbiesinger: flexbox intrinsic sizes are defined in flexbox spec.<br>
&lt;dael> Rossen_: Got it<br>
&lt;dael> iank_: I asked about it to make sure it is applied there. grid spec does use the min-content contributions directly<br>
&lt;dael> iank_: In certain circumstances<br>
&lt;dael> fantasai: yeah<br>
&lt;dael> cbiesinger: I don't think we can use that in content contribution b/c don't know content-height. We would create circular<br>
&lt;dael> Rossen_: Yes<br>
&lt;dael> Rossen_: We're getting to top of hour. Doesn't sound like we're ready to resolve on this. not quite.<br>
&lt;dael> Rossen_: Perhaps I would suggest we take it back to the issue and answer the questions there and then resolve during the F2F. Let's make sure we're not missing any of the points raised here<br>
&lt;dael> Rossen_: Let's end here<br>
</details>


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


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

Received on Wednesday, 31 March 2021 17:00:53 UTC