Update.
Due to the nature of IE, this seems to be a bit of a tricky issue. To cover what might be a problem that arises in different ways, depending on your specific situation, here are options that seem to come from a study of the participants here.
Note. Be sure to clear the cache that you have on the pages to ensure they load correctly.
Option 1:
Change the compatibility meta tag to <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" /> .
Changing from IE=8 to EmulateIE8 , you invoke DOCTYPE compatibility mode, which in turn causes IE to correctly load the font settings from the CSS file.
Option 2:
Make sure the file format you are using is in a format that IE can use and understand.
@font-face { font-family: 'Bitter'; font-style: normal; font-weight: 400; src: url(https://themes.googleusercontent.com/static/fonts/bitter/v4/XexqN1a_o27MhVVdJFKAcA.eot); src: local('Bitter-Regular'), url(https://themes.googleusercontent.com/static/fonts/bitter/v4/XexqN1a_o27MhVVdJFKAcA.eot) format('embedded-opentype'), url(https://themes.googleusercontent.com/static/fonts/bitter/v4/SHIcXhdd5RknatSgOzyEkA.woff) format('woff'); }
An important element to consider when viewing is the font file format. Now, as far as IE font support is supported, this is something like this:
- IE8 support for .eot only .
- Support for IE9 / 10 .woff and .eot formats.
Option 3:
If you use this option here, you are probably dealing with IE, sometimes with poor adoption and implementation of web standards. What is likely to happen is that IE9 displays the page in IE8 mode, but also adds native support for the .woff format to it. On the flip side, IE10 displays the page correctly in IE8 mode using the file formats that it actually supports. So my conclusion is that IE10 actually displays the page while IE9 tries to hide the disgusting standards support.
Another thought here, as you mentioned in the comments below that it seems to be working now, it is possible that Google was mistakenly doing the wrong format since the browser was IE10 but displayed content in IE8 mode. If so, then a “correct” display of IE8 will mean that the .woff file acceptable for IE10 is NOT for IE8.
Side note:
This is one of the biggest causes of problems for all web developers. The IE contest points to very low support and incorrect implementation, but is still at a disadvantage because IE comes preloaded with a very large percentage of PCs on the market, since most of them run this particular operating system. This is a very strong argument in favor of the adoption, implementation and use of standards and best practices.