Cross-browser kerning-pairs & ligatures.
This is honestly a thing of beauty. Supported currently by Safari, WebKit Nightlies, Chrom, and even Firefox by default,
text-rendering:optimizeLegibility automagically handles kerning pairs and ligatures.
How sweet is that?!
I like the idea of browsers being able to handle kerning pairs and ligatures, but sn’t it something browsers should do by default, as Firefox apparently does for text-size > 20px? Is there a reason one would want to not optimize legibility and have a CSS declaration to control that?
Some say it causes some performance hit, but Firefox had it default for some time (don’t know how long, I myself discovered this just yesterday as did many other people :)) and it didn’t bother anyone. And Chrome and Safari are faster than Firefox judging by various tests, so I guess it’s okay to have this turned on.
[…] Cross-browser kerning-pairs & ligatures text-rendering:optimizeLegibility automatically handles kerning pairs and ligatures. […]