[nayroclade]

> Inexplicably, until 2025, browsers stuck with the naive greedy algorithm, subjecting generations of web users to ugly typography.

> WebKit devs, you are awesome for shipping this feature ahead of everyone else...

Um, no? Chrome shipped this feature in 2023: https://developer.chrome.com/blog/css-text-wrap-pretty

Safari isn't early shipping this, they're late. Though not as late as Firefox, admittedly.

[notpushkin]

Hmm, I’m looking at the demo in Chrome and don’t see any difference when I turn on `pretty`: https://cdpn.io/pen/debug/xxvoqNM

In Safari, it’s a very different look.

[crazygringo]

Yeah, very weird.

Caniuse claims it's supported in Chrome: https://caniuse.com/mdn-css_properties_text-wrap_pretty

But you're right, it very clearly isn't working.

Is it a regression? Did it break and nobody noticed?

[noosphr]

So only 42 years after TeX instead of 44.

One less gripe out html I guess. Still a few hundred left.

[omnimus]

To be fair. It's not like the algorithms are not known and haven't been test implemented decades ago. The issue has always been performance. When you have composer that considers paragraphs not just lines it can get slow very quickly. TeX is compiled it doesn't matter.

I can already see when browsers implement the TeX microtypography package, everyone starts using it and everyone will be annoyed how slow browsers, html and js are.