If devs would use a font stack of maybe Helvetica Neue, Arial, Helvetica, ... this would not be such a problem but a lots of devs (working on osx) do not even care to test on Windows. So actually I find this quite a reasonable approach.
Maybe similar to some browsers (like Opera did before being blink or IE-Spartan) implementing css props of "other" browsers prefixes (-webkit ;) just because devs are "lazy".
I guess a realistic view of how the web is which may be seen :) or :(
;)
I think this is the same as http://meyerweb.com/eric/thoughts/2013/03/12/helvetial/, except maybe from the other end. I’m having trouble keeping track of all the moving pieces at the moment.
I thought that Helvetica was decent (even on PC) except at very small sizes. I always made sure to use Arial when you were under ~ 13 pt or so... and I thought PCs only replaced it for smaller sizes. Arial's uppercase 'R' is enough to bother me at any larger size.
Did you know you don't have to quote font names that have a space in them? Now you do :)
That's an interesting find. So the best practice then is to declare the Windows specific fonts first rather than the Mac ones.
@LLULL to clarify, if Helvetica is not installed, Windows will supply Arial when Helvetica is requested.