In this article we will take a look at browsers from a developer’s point of view. When developing for the Web, it is inevitable that we need to debug and test our work. How easy or how hard is it to find the problems causing errors, and how easy is it to replicate certain environment changes? Once we identify the steps we need to take to test properly, we will see if there is a chance to extend the browser to make these steps a lot easier.
Browsers as Test Platforms - Summary (Page 5 of 6 )
Surprisingly, the underdog Opera is by far the superior browser when it comes to testing and debugging Web pages. Its low market penetration and great CSS rendering engine makes it a bad test platform though, since something that looks correct in Opera might be totally unusable in IE. As an overall test browser, Firefox is the better choice. IE needs to be on every test plan though, since it still is the most used browser; but it is time to consider moving on.
Improving the existing browsers
Both IE and Firefox can be improved using third party extensions. For Firefox there is the Web developer toolbar (http://texturizer.net/firefox/extensions/#webdeveloper), which is so packed with goodies that it would make up an article on its own. One of its best features is the Sidebar, which allows you to see and edit the CSS files in use. Firefox updates the local copy of the document, not the one on the server, of course. Still, for debugging with third parties, it is a real timesaver.
Another small but significant change for Firefox is to create a new Bookmark in our Links Toolbar with the source: