> web browsers have clearly signaled that they are never going to provide better native typesetting I don’t think that’s accurate. There’s enough interest that

> web browsers have clearly signaled that they are never going to provide better native typesetting I don’t think that’s accurate. There’s enough interest that the CSS Text Module Level 4 draft expands the white-space CSS property to cover more line-breaking stuff, including a text-wrap property that lets you control the line-breaking algorithm <https://drafts.csswg.org/css-text-4/#text-wrap https://drafts.csswg.org/css-text-4/#text-wrap>; to be sure, no browser has implemented it yet, and not everything that’s in such drafts ever gets implemented, but it shows interest at the least. Firefox also has a long-standing bug for it, https://bugzilla.mozilla.org/show_bug.cgi?id=630181 https://bugzilla.mozilla.org/show_bug.cgi?id=630181, where you can see definite interest from key Firefox developers (so long as the performance hazards are managed), though they personally are unlikely to implement it, so it’s most likely to happen if someone external decides to put effort into it.