Filing this bug for an inconsistency that came up in https://github.com/w3c/csswg-drafts/issues/6794#issuecomment-1218669239 . There might already be a bug on this, but I couldn't find one right away. (bug 1740658 is similar but in fact the flex item there is also a flex container, and I think that bug and bug 1742042 are really more about sizing of flex containers based on their contents, and are distinct from this issue here.) STR: 1. Load attached testcase and reference case, and compare their renderings. ACTUAL RESULTS: They look different. EXPECTED RESULTS: They should look the same. Looking at the spec text at https://drafts.csswg.org/css-flexbox-1/#min-size-auto (mirror: https://andreubotella.com/csswg-auto-build/css-flexbox-1/#min-size-auto ), we should have both a "transferred size suggestion" of 200px and a "content size suggestion" of 100px in both cases, and we should be using the smaller one (100px) to give us the automatic minimum size. So theoretically both of these cases should be rendering with a 100px wide by 200px tall purple area here, based on the spec, I think? (Talking to Tab and fantasai just now, I think that's their expectation as well.) However, Chrome renders both cases as 200px by 200px, which is consistent but seems to possibly disagree with the spec. (Though the spec may change in https://github.com/w3c/csswg-drafts/issues/6794 )
Bug 1785914 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Filing this bug for an inconsistency that came up in https://github.com/w3c/csswg-drafts/issues/6794#issuecomment-1218669239 . There might already be a bug on this, but I couldn't find one right away. (bug 1740658 is similar, but there, the flex item is also a flex container, and I think that bug (and bug 1742042) are really more about sizing of flex containers based on their contents, and are distinct from this issue here which is focused more on flex item automatic-min-size resolution.) STR: 1. Load attached testcase and reference case, and compare their renderings. ACTUAL RESULTS: They look different. EXPECTED RESULTS: They should look the same. Looking at the spec text at https://drafts.csswg.org/css-flexbox-1/#min-size-auto (mirror: https://andreubotella.com/csswg-auto-build/css-flexbox-1/#min-size-auto ), we should have both a "transferred size suggestion" of 200px and a "content size suggestion" of 100px in both cases, and we should be using the smaller one (100px) to give us the automatic minimum size. So theoretically both of these cases should be rendering with a 100px wide by 200px tall purple area here, based on the spec, I think? (Talking to Tab and fantasai just now, I think that's their expectation as well.) However, Chrome renders both cases as 200px by 200px, which is consistent but seems to possibly disagree with the spec. (Though the spec may change in https://github.com/w3c/csswg-drafts/issues/6794 )