- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 May 2023 18:33:23 +0000
- To: public-css-archive@w3.org
OK, seems like we have three ways forward: * Define `min-content`/`max-content`/etc. to use the input size, as the WG resolved in <https://github.com/w3c/csswg-drafts/issues/2141#issuecomment-365692012>. However, @bfgeek suspects this is likely to cause compat pain. * Add `max-input` keyword to width/height that triggers this behavior on form controls, and maps to `max-content` behavior on all other elements. @bfgeek is uncomfortable with how this can mix with the existing intrinsic sizing that form controls use (like `width: fit-content; max-width: max-input;`); auto min size will still look at the intrinsic form stuff. * Add an independent `form-sizing: normal | contents` property that switches input elements to use content-based sizing in all aspects. @fantasai is concerned this is less discoverable than a width/height keyword. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7542#issuecomment-1535228386 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 18:33:25 UTC