It’s browser testing season again. Since the first Firefox 3 release candidate has been released, I will begin testing its standards support and adding it to the site. As usual, I’m going to start with the CSS section and post an update when the initial test data is complete.
Rather than using a standard test suite, I prefer to write custom tests as I go. This allows me to get into the nooks and crannies of standards support, but it does take longer. Starting now, I’m going to save all of the test cases of bugs that I find, and at some point I’ll make those test cases publicly available.
My testing process usually works like this: I initially assume that everything with a “Y” in the last version also has a “Y” in the new version, so I’m not testing for regressions in my initial test data. This saves a lot of time, and I can add regression information later as it is found. Next, I go through each “I” and “N” and retest the browser’s support. Features that still have “N” support go by quickly, so it’s the “I” features that take the bulk of my time. The time it takes to complete a section depends on a number of factors, such as the demands by my day job, how scorching hot the weather is, and whether or not the pizza has arrived yet.
In regard to Safari 3 information, that will not be part of this test session. Adding information for a new browser from scratch is a ton more work than updating for a new version, and I want to get the Firefox information out there quickly. At some point, though, I’m going to bite the bullet and do the Safari 3 testing, even if the information isn’t very thorough at first (the IE, Firefox, and Opera information started off very rough as well). Until then, here are some sites you can check out for Safari (WebKit) support information: SitePoint Reference, Wikipedia, Quirksmode.