- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Aug 2024 20:15:33 +0000
- To: public-css-archive@w3.org
> On those embedded web pages in a Web View, we're not going to give them a font size controller. Why should they need to do that? They've already expressed their font size preference in the OS settings. Why can't we respect that? Apple originally shipped Dynamic Type as a single setting for all apps on the system. Unfortunately, a large percentage of third party apps did not support the extra large accessibility font sizes, so the user's experience was pretty broken. They would constantly have to adjust the system size to its max functional size in one of these broken apps, and then readjust to their larger preferred size in other properly coded apps. To account for this problem, iOS added the ability to set a per-app font size. Likewise, the Web is full of different sites, some of which support adjustable font sizes well, and some which do not. So Safari, as the browser, added per-site font-size control. My opinion is that anything native app operated as a *browser* (includes a web view that can display an indeterminate web source) should also add a font size adjustment. In contrast to the "browser" usage of web views, any native app that includes a web view displaying known content (e.g. Electron apps like Slack) should be handling their own font size control... For example, Slack for Mac does this with Cmd +/- and/or with a "zoom preference in its app Settings. There are a dozen ways for native apps to support preferred font sizes, and IMO none of them require additional CSS features. -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2311006208 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 August 2024 20:15:34 UTC