Internet Explorer 6 is a Gorilla. Maybe even a monster. …it is to us website developers, anyway.
What I have come to realize is that the best way to tame that monster is through managing expectations. Here is why.
Outside of the Flash environment, I have always felt that pixel perfect design on the web is unattainable. Every browser and user has different font sizes, screen resolutions, color settings, and browsers. With enough time, we can get close, but we cannot get perfect. AND getting close in all the normal browsers and accounting for all the variables on individual users’ computers takes LOTS of time and continual upkeep as new browsers, computers, and devices become popular.
Those of us that work on tight budgets cannot should not program for every situation. Instead, we should program for our core users. What screen resolutions do our core users have? Are they using iPhones, laptops, PCs, or Macs? Are they using Firefox, IE, Safari, or Chrome? How old are they? Do they care about pixel perfect design or design at all?
The problem with spending lots of time coding specifically for a browser like IE6 is that as every day passes and more users bolt for IE7, IE8, and IE9, the time spent coding stuff specifically for IE6 becomes less and less valuable.
Here is what I propose.
Let’s forget about pixel perfect design in IE6, and let’s focus on content instead. Let’s create a line-item in our web development budgets for IE6. Let’s help companies make reasonable decisions about which browsers they support.
IE6 is dying. Everybody knows that. It is time that we treat it as such.
More posts from themightymo.com
A few quick things: My WordPress Maintenance Process Demo, Part 1 Transcript: You’ll see immediately after logging in, you see the 11 updates needed as well as some messages. I’m just gonna quickly read. It looks like this. I don’t need to worry about. Are you enjoying Monster Insights? Not really <laugh>. What’s to enjoy…
A site we host on Digital Ocean recently went down. It took me a lot of troubleshooting and digging before realizing that the issue was that our disk space was maxed out on Digital Ocean. The site in question needs ~20gb of space, so our 50gb server should be plenty. But alas, there it was…