It can keep you up at night, literally.  IE 6 is the browser of death and many web designers and developers have spent hours on hacks and work arounds to keep their websites working in this outdated browser.

Yeah know it’s bad when Microsoft itself is leading the charge to kill IE 6.  They’ve launched to help the cause.

As the site states, it’ve been 10 years now since IE 6 was released, it’s time to move on.  It was time to move on 5 years ago!

The graphic and data on the site is an interesting look at the main culprits.  Here in the US, while we’re down to 2.9%, it’s big corporate that is the main culprit and many of us have them as clients.

Here’s to hoping the dream comes true in 2011 and we can focus more time on better things!


1 Comment

  1. 10 years too late, there’s many tools that have come out to help get more modern functionality out of IE6, and better ways to test it when something’s wrong. First the testing. Firebug Lite has recently matured quite a bit. While I’ve moved on from Mozilla’s Firebug to Webkit’s Developer Tools, nearly every developer I know learned most of what they know about front end development through Firebug. Firebug Lite ads much of the DOM and CSS inspector abilities found in Firebug to less capable browsers by means of a well programmed iFrame. Using Firebug Lite on IE6 lets developers know why some of the bazaar placements they’re seeing happen. Now for added functionality. The HTML5 Boilerplate is a must have because it includes a collection of the best cross browser tools and compatibility helpers I’ve seen. It was put together in large part by web standards guru Paul Irish of jQuery and Google. The practices used in it are like a trophy case of geek arguments past, regarding the best ways to develop modern, yet compatible websites. First and foremost of these is the Belated PNG Fix, after many various fixes out there to allow PNGs to have an alpha channel (semi-transparent images, think drop shadows), the Belated PNG Fix has risen to the top. It’s quick, easy, and is minimally invasive. Next you have the modernizr. Modernizr does two things. It lets you use modern HTML5 tags in IE6,7, and 8. Granted, these are only tags, if the tag represents additional functionality, it wont be there. To account for this missing functionality, the second thing it does is add a series of classes to the body tag identifying what the particular browsers capabilities are, such as .no-geolocation. This lets the developer use CSS and/or javascript to fill in the functional holes with ease. The HTML5 Boilerplate also approaches CSS fixes is a novel way. It adds a class to the html tag, identifying which, if any, version of IE the browser is. This greatly simplifies browser specific IE fixes. For example to override what’s applied to the #syndication div in IE6, simply create a rule with the selector: .ie6 #syndication{} This eliminates the need to load extra CSS stylesheets, and improves load times. Lastly, if a user for some reason has Google Chrome installed, but is still using IE6, 7 or 8. It will force the browser to drop the Trident rendering engine and use Chrome’s Webkit engine inside IE. All this happens seamlessly, behind the scenes. There’s other very handy tools, such as CSS3 PIE, but the point is, development for IE6 is nowhere near as tough as it used to be. Still evil? Yes, but I like to think it’s suffering the slow and painful death it deserves. </soapbox>

Leave a Reply

Your email address will not be published. Required fields are marked *