Skip to main content

All browsers are not created equal

Actually I'm sure you all know that - it is quite revealing to look at the stats for the various websites I am associated with and look at the browser usage which varies quite considerably from site to site. On this site for example FIREFOX is the clear favourite accounting for 51% of the visitors. With another site I am associated with it is Internet explorer which dominates with 62% of the visitors using that. Over 20% of the visitors for that site are still on the dreaded MSIE 6 which is such a pain when developing web pages as is MSIE 7 to a lesser extent since they obey their own rules(1) - meaning of course a beautifully laid out web page turns to custard when viewed in these browsers and has to be tweaked to get it looking right usually to its detriment in other browsers.

Anyway below are screen prints a picture displayed in six browsers using the exact same html. The difference is remarkable.


What has happened here is a large image has been resized using HTML to a smaller size and a screen print taken of the result. Best practice of course is to resize the image to the required display size using graphics software. The images you are viewing are not scaled at all (except the initial scaling done by each browser), so hopefully the differences in results will be readily apparent regardless of which browser you are using.

Image 1
Image 2
Image 3




Image 4
Image 5
Image 6




Your mission should you decide to accept it is to match which browser rendered which image. The browsers are presented in random order and each is the most current version.

  1. Chrome
  2. Safari
  3. MSIE 8
  4. SeaMonkey
  5. Firefox
  6. Opera

Theoretically some of the browsers use the same rendering engine but each image has rendered differently regardless of that.
(1) Being a naturally curious fellow after writing this post I checked it out in various browsers. To my not very great surprise MSIE 7 mangles it slightly while MSIE 6 totally screws it up. I know why and could probably - with effort fix it. But its only a blog post after all.