Google Chrome 7

Dammit Google, fix the text-shadow bug I mentioned in my last post. Do you guys have version number envy?  Do You want to have Chrome version number higher than Internet Explorer 9?

Why am I using Google Chrome?  It’s fast as hell.  I did a cold start test – ie, right after a reboot, and it was about 3 seconds for Chrome 6, 14 seconds for Firefox in safe mode. I used the highly scientific one-one-thousand method of timing).  Safe mode means no extensions.  I also tried turning off the automatic update checks, but that didn’t help either. Chrome is also very fast and robust when you ask it do something like open 20 tabs all at once.

However, having said that, I am still using Google chrome as my default browser at home and at work.  I still use Firefox for web development (gotta have my Firebug). What can I say? Apparently, the extra 11 seconds Firefox takes to start up is in loading the text-shadow rendering.

And last, and certainly not least, it’s the browser that has the most CSS3 and HTML5 goodies to play with that isn’t from Apple.

Google Chrome 6 text-shadow is full of fail

I was upgrading Fiendish Master Plan to use HTML5 and CSS3, after being all fired up after attending An Event Apart in Washington D.C. when I encountered a major annoyance.

I have my custom embedded font working (IM Fell Great Primer)  and then I wanted to add a text-shadow to the site headline.  There’s only one minor problem – Google 6 chrome text-shadow handling is horribly, horribly broken.  The headline, which should read “Fiendish Master Plan,” reads “Fiendish.”  See the screen shot below.

Doh!  Apparently, it’s been a known issue since version 4 of Google Chrome.  If you use a custom font and put a text-shadow on it, hilarity ensues: some or all of the text vanishes. Talk about a glaring bug.

Come on Google, stop gratuitously ratcheting version numbers up every six weeks and fix the bug already.  For the record, I have commented out the text-shadow line for now.