Re: [csswg-drafts] [css-sizing-3] compressible elements with aspect ratio (#6341)

The CSS Working Group just discussed `[css-sizing-3] compressible elements with aspect ratio`, and agreed to the following:

* `RESOLVED: When we have a compressible elements also transfer a fixed min block size through the aspect-ratio to become a min inline size`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-sizing-3] compressible elements with aspect ratio<br>
&lt;dael> github:<br>
&lt;dael> iank_: The context for this is that when we've got compressible element. example min size we look at min width. If you've got min width 50px that's the min size. What nobody does with a-r is transfer min-height<br>
&lt;dael> iank_: Can get weird min width 50x and min height 100 px and a-r of 1:1 you end up with a rectangle. Proposal is allow the transfer<br>
&lt;dael> iank_: Interesting is what to do when can resolve min-height of 100%. That's what fantasai and I have been talking about<br>
&lt;dael> iank_: I'm on side of resolving % since that matches what we do with height and I think leads to better behavior. I think fantasai has concerns with that<br>
&lt;dael> fantasai: I read your reply, but haven't thought through it<br>
&lt;jensimmons> q+<br>
&lt;dael> fantasai: My concern is we have weird stuff with grid and flex with cyclic aspect of grid in particular. Don't want to resolve % in a way that causes issues<br>
&lt;dael> fantasai: Pretty sure we should transfer fixed sizes. Less sure on %<br>
&lt;dael> fantasai: I didn't notice you responding to is your table is assymetric between 2 axis and block size resolves and definite. Why not both definite or both 0?<br>
&lt;fantasai> s/didn't/did<br>
&lt;dael> iank_: That's what happens in the min/max size contributions. Resolve if it's definite and that transfers but inline axis is cyclic.<br>
&lt;dael> fantasai: I think symmetric is better<br>
&lt;dael> iank_: I don't think so. by def it's not symmertirc<br>
&lt;dael> fantasai: If height is resolved but not width it's weird<br>
&lt;dael> iank_: That's what happens, though<br>
&lt;dael> fantasai: % usually resolves in width<br>
&lt;dael> iank_: Explicitly for min/max. For inline axis they're cyclic. For block we do resolve when poss. That's how min/max works in all browsers today<br>
&lt;dael> astearns: Sounds like on that concern we should have test cases<br>
&lt;dael> iank_: Most of the test cases I've written. I can give example of how asymmetric today<br>
&lt;dael> fantasai: I think we can agree if it's fixed size it should transfer. Resolve on that and keep discussing %?<br>
&lt;astearns> ack jensimmons<br>
&lt;dael> jensimmons: Question is about use cases and not %. I have a system where an image is placed and I don't know a-r. I put on it max-wdith 100%. So that would be usually 100% but blow up if it's big.<br>
&lt;dael> jensimmons: I also do max height of 100dvh<br>
&lt;dael> jensimmons: So they I want it to be no bigger than 100vh if it's quite tall and it could shrink down a bunch becase of it's a-r.<br>
&lt;dael> jensimmons: Is that the intention of this?<br>
&lt;dael> fantasai: or that case nothing changes. Case is what happens if you have that code and a min-height or a min-width. How does that interact with your max if you put it in a shrink to fix box. What size will it end up being. In a min-content grid column current code allows the image to shrink to 0 even though has an intrinsic size<br>
&lt;dael> fantasai: If you set a min-width we won't shrink to 0. If we have a min-height instead do we transfer the min-height across the a-r to prevent collapsing to 0. That's the question here<br>
&lt;dael> fantasai: If you give it a min-height of 50px in a shrink to fix does it transfer across and have a min-width. The question iank_ has is if i set min-height 10% what do we do there<br>
&lt;dael> iank_: jensimmons I just put in a link to a case<br>
&lt;dael> iank_: fantasai I put in case 9536 to show the asymmetry we have today<br>
&lt;dael> astearns: We could resolve for the definite case. Or resolve for both definite and % and leave to fantasai to determine if % is incorrect?<br>
&lt;dael> fantasai: I'm not sure I understand the asymm issue. happy to resolve on fixed<br>
&lt;dael> astearns: Resolve on just the fixed today, then I'd want to come back next week for %<br>
&lt;dael> fantasai: Sure<br>
&lt;dael> iank_: Prop: When we have a compressible elements also transfer a fixed min block size through the aspect-ratio to become a min inline size<br>
&lt;dael> astearns: Any further discussion?<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> RESOLVED: When we have a compressible elements also transfer a fixed min block size through the aspect-ratio to become a min inline size<br>
&lt;dael> astearns: We'll come back next week for % case<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Wednesday, 4 August 2021 23:45:51 UTC