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

> Plus, my understanding of text-size-adjust is that the UA will only do the adjustment in certain circumstances, like when there's no `<meta viewport>` tag. I didn't see it working in Chrome for Android on this CodePen. I don't know if I'm missing something? https://codepen.io/joshtumath/pen/mybQmqW

Oh, I see it working on Chrome for Android:

<img src="https://github.com/user-attachments/assets/2d9ae790-cd89-4ddc-b751-f920110c248d" alt="two lines of lorem ipsum, second line is larger than first" width=300>

> > In addition to shipping `uem`, we should meet authors where they are by _also_ exposing something in env. That would allow authors to do `text-size-adjust: env(something)` to get the desired effect globally.
> 
> I'd be happy with that as well. I can imagine other use cases where that would be useful to have.

Yes. [Upthread](https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2405224736) it was mentioned that this would also allow authors to do `zoom: env(something)` if they wanted to.

> * A new length unit called `uem` (subject to bikeshedding). `1uem` is equivalent to `16px` when the user agent/operating system's font scaling is set to the default value. If the user increases the UA/OS font size by 200%, `1uem` is equivalent to `32px`.
> * A new `env()` value called `env(system-font-scale)` (subject to bikeshedding). It provides a percentage value of the operating system font scale (that the user has selected in accessibility settings). It is not affected by the display scaling for pixel density (we already have the `<resolution>` data type for that).
> 
> If there's no other thoughts, I'll add it to the agenda.

Yes! Good proposal summary, thank you.

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


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

Received on Friday, 24 January 2025 18:47:57 UTC