Post #2809174
2026-01-27 17:34 UTC
@jscholes@dragonscave.space @Lukew@toot.wales But after doing that, it became clear everyone in the group was confused by exactly how browsers do text scaling. David Grogan and I did a large investigation and we found it was so inconsistent between browsers and OSs.
And as a result of historical issues with text scaling support, the web's support for it is a mess.
And now sadly authors need to opt in to a new mode that fixes this disaster. See comparison table in explainer. https://github.com/w3c/csswg-drafts/blob/main/css-env-1/explainers/meta-text-scale.md#comparison-of-legacy-and-scale (2/2)
Replies (1)
-
@Lukew@toot.wales 2026-01-31 21:14
@joshtumath@mastodon.social @jscholes@dragonscave.space coming back to this I am a little worried that this is something we'll come to regret as yet another magical meta tag you have to add for your page to just do the right thing. Except it's less obvious when it's missing than say the viewport meta tag. I know "don't break the web" is the theme of standards but I really do wonder if in this scenario it's the right thing to do. Maybe a meta tag to opt out if you absolutely must?