• Posted by Peter Haza
  • On February 21, 2009

  • Filed under CSS, HTML, Internet Explorer Campaign, Programming, Society

  • 8 Comments

Does the Norway initiated IE6-campaign work?

Very many of you have by now noticed the national and international campaign against Internet explorer 6. Several major sites (wired, the register, digg, slashdot) picked up the story, and the word spread at an amazing speed.

The interesting question is, does it have any effect? Pål Nedregotten, Channel Manager at API, which has 50 news papers with IE6 warning under their wings, posted some stats which he keeps updating with numbers for hour by hour and per hostname. The graphs show IE6 usage Friday 13th compared to Friday 20th of February.

From the updates we can see that there actually is a decrease in IE6 usage. (Red numbers are good) At the same time we know that there are winter holidays in Norway this week, and thus we will not know for sure before 1-2 weeks have passed.

It’s also important to remember that the impact of the campaign is not not likely to be visible from day one. As has been mentioned numerous places, the biggest job isn’t to make average Joe update his machine, but getting the big companies’ IT departments to update their machines. We can clearly see this with numbers from Budstikka.no, where I work. On a typical work day we see 23-25% with IE6, while on Saturdays and Sundays we see a drop down to 10% IE6 usage.

Big companies are of course reluctant to upgrade their machines. They have everything working right now, both intranet and internet. They have also applied all possible patches to IE6 to make it more secure, so security isn’t that much of an issue. Why would they want to upgrade?

The hope of this campaign is to make direct and indirect pressure on the IT departments to update their machine parks. By putting this banner out on all possible sites, users and IT departments will be constantly reminded that using an eight-year old browser is unacceptable, especially when you think about how much www has evolved.

Hopefully this will be the push most companies need, and that they will start planning to upgrade. This however requires testing and patching before it can be rolled out. I only hope that before the summer, the IE6 numbers will be so low that we can ignore IE6 completely.

I can also reveal that on budstikka I’ve been given green light for ignoring IE6 in our new design. The reason we can do this is that we will have the old design, which supports IE6, running too, and we can just forward IE6 users there automatically by doing some user agent sniffing.

8 comments

  1. Posted by RpgFan 21st February, 2009 at 10:55 am |

    This is great news! I hope this becomes so widespread that it becomes intercontinental! Right now, the majority of the movement seems to be in Europe from what I've read over the past few hours, but I'd be overjoyed if this also happened in non-European countries too!

  2. Posted by Peter Haza 21st February, 2009 at 11:24 am |

    So do we!
    I am actually a bit surprised that not more websites outside Europe has gone with this campaign. Especially after slashdot and wired covered it.
    Oh, well, all we can do is to do our best and hope others follow. And since I work for a Norwegian news paper, at least most of our clients will have seen this warning and hopefully upgrade.

  3. Posted by Patrick 24th February, 2009 at 03:47 am |

    Hi Everybody, I run a very small web design agency in Australia and after reading this I will from now on be implementing the IE6 Warning Message on all websites we roll out. I think this is a great idea and will hopefully push our own government (who refuses to change from IE6) to finally spend some money and upgrade their system… Think how much money they will save when programmers don't have to hack the christ out of the CSS just to make a website work on their system.

    Great article!

  4. Posted by Bjørn 2nd March, 2009 at 03:39 pm |

    You don't have to use «some user agent sniffing». Use the conditional comments and meta redirection.

  5. Posted by Peter Haza 3rd March, 2009 at 12:13 am |

    This switch is done at server rendering level, not client rendering level.

  6. Posted by RpgFan 3rd March, 2009 at 01:46 am |

    If it is done at the server rendering level, you might introduce a new include file… Assuming the site was designed to be modular, this wouldn’t be difficult at all, theoretically speaking of course. Then you could use conditional comments.

  7. Posted by Peter Haza 3rd March, 2009 at 01:24 am |

    Shouldn't be difficult at all. I'm mostly worried about how we will handle the Varnish cache without much extra logic or hacks.

  8. Posted by IT Solutions 27th October, 2010 at 12:29 am |

    cheers for the post , its great campaign