- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 May 2023 19:11:33 +0000
- To: public-css-archive@w3.org
We've observed that in the wild the auto-min sizing behaviour triggers *a lot* as acting as a floor. Developers often regularly under-size flexboxes (lots of different cases, but one example is when the flexbox is a scrollable area, and sometimes authros will explicitly set a flexbox to `0px` in order to trigger this behaviour!). Flexboxes are also used everywhere now - sometimes as the "default" layout (due to the main layout that react-native supports - see https://reactnative.dev/docs/flexbox). For option (1) switching the `min-content`/`max-content`/etc to be different will result in significant compat pain. The primary concern is hanging the auto-min size in flexboxes. E.g. `<div style="display: flex; width: 0;"><input></div>`. E.g. this is triggering new behaviour even if you aren't using one of the `min-content`/`max-content`/etc keywords. For option (2) the concern is similar. You might specify something like: `<div style="display: flex; width: 0;"><input style="width: max-input"></div>` The min-content size would still be the old behaviour, leading to a weird sizing above when you had content exceeding the "legacy" min-content size, the element would size to the "legacy" min-content size. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7542#issuecomment-1535275237 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 May 2023 19:11:35 UTC