A Font Family Reunion
Go directly to Font Family Reunion or read more about it:
For my last side project I decided to redo the iconic W3C specification status banners using CSS. While that project went relatively well, with a side benefit of learning a little bit more about W3C process, one of the first questions I was asked was about the use of the local Gill Sans font instead of a web font. I immediately wondered two things:
- How strict are the W3C brand standards?
- How well supported is Gill Sans across different operating system and browser combinations?
Turns out the brand standards were not really strict, as Chris informed me later—a fallback sans-serif webfont would work fine. For the second question, things were more ambiguous. There wasn't an easy way to lookup default font lists for different operating systems, especially not specifically for ones that needed to be available through CSS
font-family. What I really wanted was a caniuse.com for default local fonts.
Building fontfamily.io #
I set out to build such a system. I already had a very nice head start, having built my own utility (
fontfaceonload) to test if remote web fonts had loaded successfully. You might remember this utility from my research into icon fonts. It only required a few minor tweaks in order to test local fonts in addition to remote fonts. Of course, none of this is necessary if you have the CSS font loading API available to you, but I wanted to test operating system and web browsers that were older than the newly minted native API.
If you’re curious how
fontfaceonload works internally, documentation is available on GitHub.
But there was another hurdle. There is no API through which you can retrieve a list of all the installed fonts, so I had to compile a list manually. If you have access to the shell on the host operating system, *nix machines provide a
fc-list command to retrieve a list of installed fonts. Also, most operating systems actually publish a list of installed fonts on the web in their support pages, so I compiled one big giant list of font families from a bunch of these sources.
The test page then iterates through the list and tests over 1000 different font family names to see if the current browser supports them. I used Browserstack for most of this, as well as one of the best perks of working at Filament Group, a home device test lab. Running the test page on a bunch of devices and virtual machines gives us a nice list of results: the default installed fonts.
Default Keywords are Browser Madness #
But that’s not all. Font Family Reunion will also tell you what the five standard CSS keyword font-families are aliased to in each operating system. They are
monospace, and the lesser known
cursive. This is where browsers diverged from operating system standards into browser specific behavior. Browsers have made their own decisions about what the defaults should be and boy do they vary.
Predictably, many browsers defer to the default web browser’s default fonts, especially on Mac OS and iOS (Safari). If you’re gonna use
font-family: fantasy on an Apple device, it’s gonna be Papyrus (stylistically probably a bad choice, but at least it’s consistent).
Then you open up Windows. On Windows, default fonts are a free-for-all, even between versions of their own browser, Internet Explorer.
shout out to whoever changed `font-family: serif` from Times New Roman to the Korean typeface Batang in IE9 and IE10 http://t.co/ApjQsjXXYC— Zach Leatherman (@zachleat) September 22, 2014
font-family: fantasy is aliased to four different typefaces across six different browsers on Windows 7, and three different typefaces across four different browsers on Windows 8. Unless you think that Impact and Papyrus look alike (they don’t), I would stay away from
font-family: fantasy for now.
It was also interesting to note that on Windows 7 and up, both Chrome and Opera decided to forgo the standard
monospace favorite of Courier New (on Windows) and instead go with Consolas, a newer and better Microsoft creation. Given the free-for-all that is default keywords on Internet Explorer, I would have guessed that Microsoft would be more progressive with their
monospace choice—but I’ll leave that to the missed connections section on Craigslist.
The other little factoid that Font Family Reunion exposed is the Mac/Windows duel that is Helvetica/Arial and Times/Times New Roman. Did you know that on Windows, Helvetica is aliased to Arial but on Mac both Helvetica and Arial are available separately? Same with Times (aliased to Times New Roman on Windows) and Times New Roman (available on both). So,
font-family: Helvetica, Arial and
font-family: Arial, Helvetica operate much differently.
And if all of that wasn’t confusing enough, Android tries to be tricky and uses typefaces that are not actually exposed through CSS font-family. It keeps them hidden behind aliases. Droid Sans is available as an explicit font-family name, but Droid Sans Mono (the default monospace) and Droid Serif (the default serif) are not.
A Manageable Mess #
So, what have we learned? The rules keep things pretty simple:
- Always specify a default CSS keyword fallback, don’t let the browser use its own default choice of serif (it doesn’t necessarily even match
- Don’t use
- Don’t go overboard with your stack.
font-family: Arial, "Helvetica Neue", Helvetica, sans-serif;is the first stack listed on CSSFontStack.com. Running this through fontfamily.io reveals that Arial is used everywhere (and aliased on Android). The middle two families are never used.
Remember, when you’re using
@font-face to load custom web fonts, the fallback font-family experience—what shows while the remote font is loading—is important too. Maybe you could even go without using a few custom web fonts, or not use any at all? It’s certainly worth asking the question.