- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Feb 2023 20:14:10 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-flexbox][css-grid] Automatic minimum size on replaced element with `overflow` different than visible/clip == https://software.hixie.ch/utilities/js/live-dom-viewer/saved/11339 ```html <div style="display: flex; width: 50px;"> <canvas width="1" height="1" style="background: blue; height: 100px; overflow: visible"></canvas> </div> <div style="display: flex; width: 50px;"> <canvas width="1" height="1" style="background: cyan; height: 100px; overflow: scroll"></canvas> </div> ``` There is interoperability that in the 1st case the automatic minimum size makes the flex item be 100px, and in the 2nd case the automatic minimum size is avoided due to `overflow: scroll`. However, https://drafts.csswg.org/css-flexbox-1/#min-size-auto says "a flex item that is not a [scroll container](https://drafts.csswg.org/css-overflow-3/#scroll-container)". And the `<canvas>` is replaced, so it's not really a scroll container? Should the spec check the computed value of `overflow-x/y` instead of being a scroll container? Should browsers change? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8502 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 February 2023 20:14:11 UTC