Yelotofu

Yelotofu ~ “In building standards compliant sites we are creating a better Web for the future.”

Happy Birthday Google Chrome!

Wow, it's been a year already? Time certainly flies when you're having fun! It seems the Google Chrome team have been hard at work! They've finally made a version of Google Chrome for Mac and Linux which you could download from the Dev channel.

Had a quick test and found Print and Application shortcuts haven't been implemented yet. Chrome also died on me a few times unexpectedly (doesn't seem to cope too well with our QUnit test pages). Overall I like the minimal interface and speedier JavaScript response times. It could only get better!

Browser testing: How do you do it?

Andy Clarke, the author of Transcending CSS, started an interesting discussion on CSS Browser Testing Order. It's surprising how we more or less test in the same order. I place Windows XP first though as I'm primarily a windows user and my clients are usually on Windows too.My CSS browser testing order

  1. Firefox / Opera on Win XP
  2. Internet Explorer 7 on Win XP
  3. Safari / Firefox on OSX
  4. Netscape 7 & 8 on Win XP
  5. Internet Explorer 6 on Win XP

I don't usually worry about browsers older than those listed above unless the client has a specific requirement. I've also found that Safari renders as if it were a cross between Firefox & Opera on Windows XP, so if it looks good in both browsers it should look near perfect in Safari on OSX.

As you may well have noticed, IE6 is last. The rule of the game is to test your browsers in order of most compliant then work around the lesser compliant ones and even use a hack or two for those that refuse to obey—namely IE6. If you test your work with this mindset, browser testing would never be a nightmare and may even be fun! Well, sometimes fun. ;)

This testing order is by no means a rule of thumb, it's just the way that works for me. I'd be interested to hear how you do it.