I'm not sure our best practices for responsive & fluid #CSS typography are actually *the best*.

On my own site, using the widely accepted approach, a user preference of 16px gives me ~24px font. A pref for 24px gives me ~36px.

Where did we go wrong?

https://www.oddbird.net/2025/02/12/fluid-type/

Reimagining Fluid Typography

Are we responding to the right inputs?

OddBird
@mia @aardrian Cool articles, thank you. With a screen & media query environment, dvw unit helped me a bit for scaling sizes. That was the last state of font-size refabrication for me, looking forward to have a solution of small amount #CSS codes.
```
--header-title: calc(2rem + 1dvw);
```
@mia @aardrian Oh, that is useful. Hopefully most publicly-facing web designers know about this.

@mia typo in code example

```
html {
font-size: calc(1em, 0.9em + 1vw, 1.5em);
}
```

clamp, right?

@mattwilcox Thanks, should be fixed as soon as it re-deploys
@mia If I’m not mistaken, once we have unit algebra in calc() or calc-mix() and progress(), shouldn’t it be possible to do entirely in CSS at runtime without assuming anything about px-per-rem?
@noleli I'm not sure what "it" is in this sentence. I'm less worried about doing something at runtime in CSS, and more worried that we're doing the wrong thing in the first place.
@mia fair! I was thinking about the Utopia approach but without assuming 16px/rem, so if someone increases their root font size pref the ratios between the steps of the type scale are all retained, and nothing gets prematurely clamped. But your idea of a subtly responsive root font size is definitely something to ponder 🤔
@mia Hm hm hm, I have some ideas re: all of this, will need to write a blog post :D