- From: Oriol Brufau via GitHub <noreply@w3.org>
- Date: Sun, 24 Aug 2025 22:41:35 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-flexbox] Should automatic minimum size check scrollability in the main axis or both? == https://drafts.csswg.org/css-flexbox/#min-size-auto > the used value of a [main axis](https://drafts.csswg.org/css-flexbox/#main-axis) [automatic minimum size](https://drafts.csswg.org/css-sizing-3/#automatic-minimum-size) on a flex item whose [computed](https://drafts.csswg.org/css-cascade-5/#computed-value) [overflow](https://drafts.csswg.org/css-overflow-3/#propdef-overflow) value is [non-scrollable](https://drafts.csswg.org/css-overflow-3/#non-scrollable-overflow-value) is [...] #12289 allows `overflow` to be scrollable in one axis but not the other, so we need to decide if the above will only check the main axis, or whether we still want to check both. ```html <!DOCTYPE html> <style>body > div { display: flex; width: 0; white-space: nowrap }</style> Has automatic minimum size: <div> <div style="overflow: clip; border: solid">...</div> </div> Automatic minimum size is zero: <div> <div style="overflow: hidden; border: solid">...</div> </div> Automatic minimum size was zero. What now? <div> <div style="overflow: clip hidden; border: solid">...</div> </div> ``` I'm leaning towards just checking the main axis. Note that WebKit isn't following the spec: it zeroes out the automatic minimum size if `overflow` is not `visible` in the main axis. So I don't think we are constrained by web compat. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12650 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 24 August 2025 22:41:36 UTC