W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2020

Re: [csswg-drafts] [css-sizing] clarification around Compressible Replaced Elements and min-content size (#5665)

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Wed, 09 Dec 2020 23:04:46 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-742119407-1607555085-sysbot+gh@w3.org>
Some of those bug reports are kind of old, so I just retested a few of them (Heineken, Yahoo, Bing) in Firefox with RDM mode (with Galaxy S9 as the choice of emulation target), and I confirmed the bugs are indeed still reproducible on those live sites. :(

It seems that this is a mobile web-design trick that's spread somehow (or been repeatedly rediscovered?) as a way of creating a textfield/button combo that fills the available width in a mobile viewport; the web developer just wraps them in a flex container and gives the textfield `flex:1;width:100%`, and they expect that to make the input compressible (and it does, in Chrome/WebKit, which means nearly-everywhere on mobile).  Kind of like https://jsfiddle.net/dholbert/21jpntL9/

So, it does look like our hands are tied here.

GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5665#issuecomment-742119407 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 December 2020 23:04:47 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:23 UTC