- From: Alice Wonder <alice@domblogger.net>
- Date: Mon, 8 Jan 2018 15:23:06 -0800
- To: "Belov, Charles" <Charles.Belov@sfmta.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style list <www-style@w3.org>
On 01/08/2018 03:13 PM, Belov, Charles wrote: >> -----Original Message----- >> From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] >> Sent: Monday, January 08, 2018 1:58 PM >> To: Alice Wonder <alice@domblogger.net> >> Cc: www-style list <www-style@w3.org> >> Subject: Re: CSS-4 and min|max-device-width >> >> On Mon, Jan 8, 2018 at 12:31 PM, Alice Wonder <alice@domblogger.net> >> wrote: >>> On 01/08/2018 12:03 PM, Tab Atkins Jr. wrote: >>>> then what you actually want is to discriminate based on the >>>> resolution of the device, which is also available via MQ.) >>>> Pinch-zoom never causes reflows (unless it's buggy), and text >>>> wouldn't change due to it either. > > At risk of introducing a side-issue - I'll be happy to start a new thread if you'd prefer - pinch-zoom not reflowing is a bug to me. It makes many websites unusable for me on mobile because I find their fonts too small. Pinch-zoom without reflow adds sufficient cognitive load for me that when I have to scroll for each line in each paragraph in order to read the full line because it hasn't been reflowed, then I don't really grasp the content. So I wind up waiting to read long-form content until I'm at a desktop, which does reflow when I zoom. > > I acknowledge that knowing the device dimensions doesn't help with this, but calling pinch-zoom reflow buggy is counter to what I would find good experience. That said, if browsers and CSS were to support the iPhone's Larger Text setting (under General > Accessibility), that would be a partial workaround (depending on how much larger the site made the type before flowing the text). > *snip* Yes I think it would be great if users could set a standard font size that overrides the font size specified in CSS as the base font size. My personal experience is most pages where the font is too small, the website is not using viewport metatag and what mobile browsers do in those cases is render as if the viewport was larger than it actually is and then shrink the rendered image to the device - resulting in small fonts that are hard / often impossible to read. Hopefully that problem is being reduced as more and more CMS systems start using the viewport metatag by default with responsive design.
Received on Monday, 8 January 2018 23:25:12 UTC