If you’re still reading this blog you must be a real fan. Or just plain bored. So I’ll indulge you with some entertainment.
You would’ve noticed by now how rebelpixel.com looks very different to how it has always been for some years now. I always liked it grey. Now though, it’s in boring white that I think is quite a refreshing change. (You wouldn’t know that though if you’re reading this in an RSS reader.) But I guess “fresh” wouldn’t be staying for long.
If you’re reading this on a Mac with a fairly recent browser, you’d think the new minimalistic look blends well with the @font-face embedded font I’m using: Museo Sans. This works in Firefox 3.5 (and the recently released 3.6), Safari, and Google Chrome. Unfortunately, if you’re on Linux or Windows, @font-face rendering can go bad. In my current case, really bad. Look:
Firefox/Mac text rendering just blows aways its Firefox/Windows counterpart, though I honestly feel it’s more of the operating system’s fault. Google Chrome shows us the same trend:
Note how Chrome (and Safari as shown below) renders the text inside <blockquote> tag. It’s supposed to be in italic as defined in CSS though I did not declare an italic sub–font for Museo Sans. Firefox tries to make italics out of the single embedded font file while it’s ignored in Webkit–based browsers. What should be the right behavior? I honestly have no clue.
Internet Explorer 8 on Windows 7 paints a different picture: it ignored my EOT–encoded fonts and simply rendered text using the next available typeface in the CSS font stack. It’s broken and familiar; silently I think I’d rather take that compared to the rendering inconsistencies in embedded fonts.
Welcome to web design in 2010—it’s almost just like a decade ago.
Now I should really fix this design.