“Bulletproof” font fallbacks, and more changes to browser support
We’re making a few changes to our browser support that will improve the web font serving experience in a few new places. In this post, we’d like to walk you through those updates.
Introducing “bulletproof” CSS font fallbacks
But we cannot reliably detect every browser correctly. For that reason, today we are introducing a “bulletproof”
@font-face fallback format in addition to our normal browser detection. This means that instead of serving no web fonts to unrecognized browsers, we serve a special CSS file that gives the browser several font formats. The browser can then select the most appropriate format. While this is less efficient than our default solution, it means improved web font support for lesser-known and unsupported browsers.
Dropping support for some browser versions
Going forward, we are no longer supporting the following browsers:
- Chrome 4 and 5
- Opera 10
- Firefox 3.5
These browsers are no longer supported by their vendors, and all have very low usage. Fortunately, thanks to the new “bulletproof”
@font-face fallback format, we will still be serving fonts to these browsers — so in practical terms nothing will change.
Now serving OpenType fonts for Android
We are also making some changes to our support for Android 3.1, 3.2, 4.0, and 4.1. We used to serve SVG fonts to these browsers, but going forward we will be serving OpenType fonts. This will improve text rendering and performance on those browsers. By using embedded OpenType fonts we also reduce the number of HTTP requests, resulting in a smaller and quicker font download.
Republish your kits