Re: [csswg-drafts] [css-fonts][css-viewport] UAs inconsistent in how OS font settings affect the default font-size `medium` (#10674)

> > Chrome on Android allows the user to increase the UA and OS font sizes independently (I think Chrome on Windows also). If the user increases the UA and OS font sizes by 150% _each_, would `1uem` be equivalent to `36px` because 16px * 1.5 * 1.5 = 36px? And `1rem` would be equivalent to `24px`, same as it is today?
> 
> It depends on if we're talking about the individual page zooming feature, or the browser's settings.
> 
> But it's a good question and I think it brings us back to the original issue of how UAs are inconsistent in what `font-size: medium` actually is. Firefox for Android is the only mobile browser AFAIK that responds to the OS font size setting. It has an option to let the user choose whether to use the OS setting or _override_ that with an app setting. But they are never combined.
> 
> In my opinion, that feels like the right solution: choose either the OS or UA font sizing, and preferably let the user decide which.
> 
> ![Screenshot of Firefox accessibility settings page. First option is a switch with the label, 'Automatic font sizing: Font size will match your Android settings.'](https://github.com/user-attachments/assets/5d66fb72-0d22-44b7-b33f-a67e45fdd629)

Thinking about it more, I don't know if CSS can require a UA to honor only one user preference and not combine multiple user-supplied signals. I don't know that we'd want CSS to do so even if it can.

I agree that Firefox's approach is superior though. https://crbug.com/40928643 is the chrome bug to do something similar.

Also, thanks for the usage examples. Makes sense.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 22 January 2025 01:24:20 UTC