Devs ditch IE6 support, charge for IE7

Poll shows clarity in working with Microsoft’s browser

Devs ditch IE6 support, charge for IE7
IE6 is finally out, according to a dev survey. IE7 clings on, but many devs charge for support

Mobile platform strategist and consultant Peter-Paul Koch has revealed the results of his poll about usage of old versions of Internet Explorer among web designers and developers. The aim of the poll was to ascertain which versions of Internet Explorer were still being supported by developers, why they were being supported, and also how they were being detected. According to Koch, his main goal was to “find out what kind of old IE information web developers need”.

The worst-answered question in the poll still had well over 1000 responses, and Koch explained that preferences within the industry were very clear. IE5.5 is now dead in the water, and only a small number of developers are required to support IE6. For the majority, IE7 remains a going concern, with 56 per cent required to test in it, and 79 per cent having tested at least once in that browser during the past year. By contrast, 92 per cent were required to support IE 8.

A fact that surprised Koch was the number of developers charging extra for projects that work in older versions of IE: a relatively low 66 per cent in IE6, but a surprisingly high 42 per cent in IE7. In terms of detection, there were no surprises, though, with conditional comments winning out far over the IE versioning switch and the antiquated Quirks Mode, which reverts IE behaviour back to version 5.5, enabling developers to temporarily pretend their PC is a TARDIS that’s propelled them back to 2000.

With the results forming a well-researched sanity check, Koch concluded he’d no longer test by default in IE6. Let us know in the comments if you’ve also ditched support for Microsoft’s ageing browser.

12 comments

Comment: 1

Yep, Ditched IE6 support over a year ago. Still test for IE7+.

Comment: 2

IE6 and 7 are dead in my shop. We just don't see the traffic that would justify supporting them. It's time that more devs and shops start charging for or ending support for older versions of IE.

Comment: 3

I ditched IE6 a long time ago - when it celebrated its 10th birthday, it was time for it to be retired. Still have a little glance at how new sites look in IE6 every now and again, just for the fun of it. I'm supporting IE8 and testing in IE7 to ensure sites work, but not support any little visual enhancements.

Comment: 4

The idea of charging specifically for IE7, given how few spanners it throws in the works if you have a sensible development plan, seems over the top. If these people mean that they factor the time-cost in to their quote then fair enough, but if it's some kind of "bolt-on" then it feels a little too much like a con rather than professional practice...a way of creaming extra money off of a less knowledgeable client.

Comment: 5

Not sure why people would support IE7 if they don't support 6. IE7 has a fraction more support than IE6 but between them it's about 1% according to Statcounter. If you're ditching one then surely ditch the other (as we have).

Comment: 6

Ditched both 6&7 - as soon as you start charging extra for IE7 support suddenly not a single client is interested anymore.

Comment: 7

Shouldn't it depend on the user base? If you have a lot of users on IE7 you can't really ignore it.....

If a client wants it and their user base shows a demand then by all means charge extra for the time, but you should never really say yes or no to certain browsers until you look at the usage stats for that specific project.

Comment: 8

Shouldn't it depend on the user base? If you have a lot of users on IE7 you can't really ignore it.....

If a client wants it and their user base shows a demand then by all means charge extra for the time, but you should never really say yes or no to certain browsers until you look at the usage stats for that specific project.

Comment: 9

We support the last three released versions of common browsers as standard; anything else is an extra.

Dealing with corporate global clients dictates IE6 can still be a requirement, if for example, you are targeting China: the last remaining place on the planet with >20% usage.

Comment: 10

Working with a large furniture manufacturer, we're still required to support IE7, but we did start charging for it as well this past year.

Comment: 11

We still support IE7 (ditched IE6), as Sod's Law says there will always be the friend of a friend of the mother of the person who commissioned the website who is using that browser and makes us look totally unprofessional if we don't support it... Sigh!

Comment: 12

As a Software Tester, in an ideal world, we should only test on the latest version of each browser as backdating and testing every version of every browser would just lead to exhaustive testing. The majority of sites we create for our clients use the latest technologies such as CSS3 or HTML5 and therefore, hacks are needed to make certain styles and fucntions work in the older legacy browsers. However, the majority of our clients ask us to either support IE7/IE8 or atleast try to reflect the same functionality in older browsers. Clients usually ask for this as they have a section of the market which still uses the old browsers.
I'm personally all for dropping support of legacy browsers and forcing users to update. They would have less bugs in the long run and a better quality of product. I would prefer to have an approach of displaying a user friendly message to upgrade browser when opening the page in an older browser. For example, if you open YouTube.com in IE7 now, Google now have a message which tells the user IE7 is no longer supported. More companies need to do this so we can drop support for older browsers.
June issue on sale now!

The Week in Web Design

Sign up to our 'Week in Web Design' newsletter!

Hosting Directory
.net digital edition
Treat yourself to our geeky merchandise!
site stat collection