> I'm putting my email on GitHub precisely to give people a way to contact me.
They’re not only looking at the public email in your profile, they’re also looking at your committer email (git config user.email). You could argue that you’re not putting that out for people to contact you.
(I’ve used that trick a couple times to reach out to people, too, but never mass emailing.)
"While support for pretty shipped in Chrome 117, Edge 177, and Opera 103 in Fall 2023, and Samsung Internet 24 in 2024, the Chromium version is more limited in what it accomplishes. According to an article by the Chrome team, Chromium only makes adjustments to the last four lines of a paragraph. It’s focused on preventing short last lines. It also adjusts hyphenation if consecutive hyphenated lines appear at the end of a paragraph."
The article goes on to talk about how it's up to the browser (and not necessarily permanent) about how to handle the setting, and furthermore a new
value was agreed upon to do what Chromium was doing, called "text-wrap: avoid-short-last-lines".
Ah, OK. I finally got the demo to show a difference under one specific window width, where it changed the last line of a paragraph from one word to two words.
So it does exist... but yeah, barely does anything. Thank you for finding the explanation!
> Although Safari is the first browser to ship a non-joke implementation of text-wrap
(Emphasis mine.) Chrome is using a different algorithm for this, which probably fixes some typographic problems, but defaults to greed most of the time.
I’m looking at the comparison [0] and the `pretty` example is hyphenated, while greedy is not. Not sure it’s fair to compare them like that, considering we’ve had `hyphens: auto` for a while now.
Edit: it’s actually vice versa! Which I should have known because the very next paragraph says:
> But the “smart” algorithm decides to add an entire line to it, which requires inflating all the white space proportionally.
Which is exactly how the example on the right looks.
That jumped out at me too... I'm not sure if they have different hyphenation properties set though, or if the greedy justified version just doesn't wind up hyphenating anywhere in this particular case?
Unfortunately there's no live HTML demo to inspect, just the images.
Playing around with it, seems that Safari simply stops hyphenating entirely when when text-wrap is pretty, regardless of whether it's justified or not. (If you smoothly resize the browser width, it makes it pretty easy to tell if hyphens ever come up.)
Which means the image on the left seems like it might be the wrong image?
And now I wonder if text-wrap: pretty is supposed to avoid hyphenation? Are hyphens not pretty? Or is it just a partial implementation by Apple, that they haven't gotten around to supporting hyphenation for it yet?
You can get it if you carefully adjust the window width! Or there’s one example in the author’s post – the word “implementation” is hyphenated for me [1].
So it looks like the algorithm tries to minimize hyphenation, which makes sense to be honest.
Ha. Oh wow. OK, I got "implementation" to hyphenate... but only once I changed the zoom level, and only for one specific exact window width. One pixel narrower or wider, and it stopped hyphenating.
So hyphenation exists in theory, but I'm just going to go ahead and say that however it's tuned seems completely broken.
Again, I think it’s very deliberate :-) Hyphenated words are slightly harder to read, so it makes sense to avoid them – maybe not as zealously, though.
reply