- From: Josh Tumath via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 May 2025 23:17:24 +0000
- To: public-css-archive@w3.org
> [@davidsgrogan](https://github.com/davidsgrogan) That explainer is _amazing_. Can we publish it as a Note or something? (btw: your `@media` code example seems to be missing something) Oh thank you for spotting that. I've just fixed it. > Lastly, I'm intrigued by [@frivoal](https://github.com/frivoal)'s suggestion, since it would neatly solve the `@media` use cases as well as plugging into the cited advantages of the "initial font size" alternative. I'm not generally a fan of viewport-meta stuff, but in this case it might be worth it: the developer experience would be a lot more consistent, with fewer things to learn and juggle, if we can enable the font sizing system that CSS was originally designed to have. That's actually something @davidsgrogan, @progers and I are currently discussing! I'm excited about it, too, if we think it's worth revisiting. On that note, when I explained our proposed solution to some authors at a recent conference, most of them just said they didn't want to have to think about this problem and that the CSSWG should just 'fix `rem` units' (meaning make the initial UA font-size use the OS font scale). So I suspect they would much prefer the `<meta viewport>` solution (or some at-rule equivalent). As explained in the original post, most authors are just taught to size things using font-relative units, so I think they would love to just have a switch that means 'make `rem` units work the way I expect them to by respecting the OS font scale'. -- GitHub Notification of comment by JoshTumath Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2914411861 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 May 2025 23:17:25 UTC