Wednesday, December 24th, 2008
Steve Souders has updated his UA Profiler tool that tracks the performance traits of various browsers. Being able to drill down and see the differences from build to build is great stuff, and here are all the new features:
Previously, I had one label for a browser. For example, Firefox 3.0 and 3.1 results were all lumped under “Firefox 3?. This week I added the ability to drilldown to see more detailed data. The results can be viewed in five ways:
- Top Browsers – The most popular browsers as well as major new versions on the horizon.
- Browser Families – The full list of unique browser names: Android, Avant, Camino, Chrome, etc.
- Major Versions – Grouped by first version number: Firefox 2, Firefox 3, IE 6, IE7, etc.
- Minor Versions – Grouped by first and second version numbers: Firefox 3.0, Firefox 3.1, Chrome 0.2, Chrome 0.3, etc.
- All Versions – At most I save three levels of version numbers. Here you can see Firefox 3.0.1, Firefox 3.0.2, Firefox 3.0.3, etc.
- hiding sparse data
- The result tables grew lengthy due to unusual User Agent strings with atypical version numbers. These might be the result of nightly builds or manual tweaking of the User Agent. Now, I only show browsers tested by at least two different people a total of four or more times. If you want to see all browsers, regardless of the amount of testing, check “show sparse results” at the top.
- individual tests
- Several people asked to see the individual test results, that is, each test that was run for a certain browser. There were several motivations: Was there much variation for test X? What were the exact User Agent strings that were matched to this browser? When were the tests done (because that problem was fixed on such-and-such a date)? When looking at a results table, clicking on the Browser name will open a new table that shows the results for each test under that browser.
- Once I sat down to do it, it took me ~5 minutes to make the results table sortable using Stuart Langridge’s sorttable. Now you can sort to your heart’s content. (This weekend I’ll write a post about how I made his code work when loaded asynchronously using a variation of John Resig’s Degrading Script Tags pattern.)
Posted by Dion Almaer at 6:16 am