I’ve got some information on this problem now. It appears to be Google Chrome related- specifically, the latest version: Chrome 33. It’s not rendering the Google fonts properly, and giving developers fits. I have a temporary fix that’s working for me. Credit goes to rafikibubu in Google Groups.
As long as you have the Google fonts defined as usual in your code, the following can be placed in the <head> section of your PHP file. Essentially, it forces Chrome to load the fonts again. They may take about 3-4 seconds after page load, but it’s better than nothing:
<script>
WebFontConfig = {
google: { families: ['FontOne', 'FontTwo'] },
fontinactive: function (fontFamily, fontDescription) {
//Something went wrong! Let's load our local fonts.
WebFontConfig = {
custom: { families: ['FontOne', 'FontTwo'],
urls: ['font-one.css', 'font-two.css']
}
};
loadFonts();
}
};
function loadFonts() {
var wf = document.createElement('script');
wf.src = ('https:' == document.location.protocol ? 'https' : 'http') +
'://ajax.googleapis.com/ajax/libs/webfont/1/webfont.js';
wf.type = 'text/javascript';
wf.async = 'true';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(wf, s);
}
(function () {
//Once document is ready, load the fonts.
loadFonts();
})();
</script>
You may want to specify the fonts in the above code, but it seems to be working as is. As I said, this is only a temporary fix. Hopefully Chromium gets this huge problem fixed ASAP.
*Edit* Thanks for the link above. It appears it is fixed for the forthcoming versions of Chrome.
