Re: [csswg-drafts] [css-env][css-fonts] New `<meta text-scale>` tag to make UA initial font size respond to OS text scale setting (#12380)

Great feedback, thank you!

> In general I hate these `<meta>` things, but I think for this use case it makes sense, and I agree 100% that letting `rem` units behave as intended is a better author experience. Some things to think about:
> 
> * Use `compat` or `fixed` and `user` or `adjustable` as the keyword values for the `<meta>`? Since that better reflects that the initial value is fixed at 16px for compat, and the new value is intended to match user adjustments.

Well, the initial value isn't always 16px. On desktop browsers it is 16px × UA-level scale (see [table](https://github.com/w3c/csswg-drafts/blob/main/css-env-1/explainers/meta-text-scale.md#comparison-of-legacy-and-scale))

> * Remap the other absolute size keywords appropriately so that they also scale with `medium`.

Yes! We planned to do this but appear to have omitted it from the explainer by accident.

> * Consider remapping the other absolute font-size keywords in a way that reflects the OS text scale, which IIRC doesn't always scale linearly with the body text size.

This is an interesting idea. I don't think we'd want to do both this AND [`progressive`](https://github.com/w3c/csswg-drafts/blob/main/css-env-1/explainers/meta-text-scale.md#non-goals-for-now:~:text=This%20automatic%20non%2Dlinear%20scaling%20could%20be%20supported%20via%20a%20future), but maybe. Or maybe if we do this, we won't need `progressive` at all.

> * Maybe also allow these keywords in `calc()` etc. so that authors can interpolate those sizes, too?
> * Recommend to authoring tools that they offer simulation of various size preference _including accessibility settings_ (which are not always available without an opt in, and can be significantly larger than the author might expect otherwise), to help make sure authors write pages that work for all users.

Agree that nudges from author tooling would go a long away toward ensuring these `<meta>`-enabled pages work well for all users.

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


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

Received on Wednesday, 2 July 2025 01:30:30 UTC