This is a test headline
Here is a link to follow to get you started yourself: Quick Start, Google font directory
And yes, it looks like Google is indeed serving up css where the specified font family is linked via obfuscated URL at a googleusercontent subdomain (themes). Browsers will behave a little differently.
Chrome will render the page, but until the font has loaded, there will be a blank space in it’s place. Firefox will render default font text and once the font has loaded, replace the text. It’s called “flash of unstyled text.” Safari renders like Chrome. Internet Exploder renders like Chrome as well.
3 thoughts on “A test post using Google’s font directory beta”
Well, this doesn’t work on an iPad because i am writing this comment on mine and the style sheet is defaulting for me. Maybe the 4.0 this Fall for iPad will bring support for it.
Strangely enough, the blog title renders fine in IE8, but the body font does *not* work.
Also, fonts look really bad in Windows 7 (at least w/my settings) in pretty much every browser (including Safari.)
The “Josefin Sans Std Light” is really light and washed out. Tangerine looks ok in some browsers, but blocky in others. However, this is what I was seeing on the Google Fonts API page too.
I am not sure how I feel about this right now. I have been doing my own CSS3 font embedding thing for a while on internal projects where I know the browser to be used. Doing that, I have much more control.
Now in regards to Windows 7, I have no answer. I wonder if Google’s implementation isn’t quite up to snuff yet. I did a double font load, perhaps that’s not working for Internet Exploder yet?