- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Feb 2022 17:46:42 +0000
- To: public-css-archive@w3.org
@dholbert - Given that clarification I think there is still a terminology issue here. E.g.
```html
<div style="display: flex;">
<!-- Chrome says final width is 50px. Firefox says 100px. -->
<div style="background: blue; height: 100px; aspect-ratio: 1/2; ">
<div style="width: 100px;"></div>
</div>
</div>
```
> The flex item in question does not have a specified size suggestion, and is not replaced, and therefore it falls through to the final clause and uses its content size suggestion which is its min-content size in the main axis (100px). Therefore Firefox's behavior here is correct.
In the given example (afaikt) the min-content size (given that it has an aspect-ratio) is actually `50px` not `100px`.
One thing that might mitigate the confusion here is to change the definition of `min-content` such that when we compute it we look to see if `min-width: auto` is present.
Ian
--
GitHub Notification of comment by bfgeek
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6794#issuecomment-1028193403 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 February 2022 17:46:44 UTC