The Government of Canada Stops Supporting IE6

Submitted by mgifford on

I'm happy to hear of the Government of Canada's recent announcement that they will no longer be supporting Interent Explorer 6.  This is not an easy decision as many government departments chose to develop applications for a single proprietary browser rather than based on international standards. It will be expensive to retrofit many outdated systems, but it is important to fix what is widely understood to be tragically short term thinking.

Although IE6 held considerable market share historically, many security problems are causing governments around the world to officially drop support of this old browser. Both hackers & foreign government agents are able to hack the system to gain access to critical systems in governments and business.

Google's reduction of support for IE6, starting last month, is also a consideration. So many Web 2.0 tools are connected to Google these days and with the government looking to connect more with it's citizens, this is going to be a problem.

Furthermore, IE6 has many quirky features which make it very difficult to design for. By not adopting standards compliant browsers earlier the Government of Canada has wasted millions of dollars by having to insert CSS & Javascript hacks to insure that their sites can work for both IE6 & modern secure browsers like Firefox, Chrome & Opera

Although there was interest in considering moving ahead to the stable IE7 or IE8 releases, or even development releases' of IE9. Some even considered adopting open source browsers like Firefox which would allow security experts to fully evaluate and customize releases for our government.

However, our government has decided to roll back the officially supported browser to IE5.  Although no longer officially supported by Microsoft, it's clear that Microsoft isn't keeping up with security support for IE6 anyways.  Also moving back to IE5 ensures that important government <BLINK> & <MARQUE> tags will work again. As an added bonus, government security experts have dug up the security certificate for this software.

Image of search ranking for government Canada IE6Sadly the notice that IE6 was no longer going to be supported in the Government of Canada was just an April Fools' joke. Like so many other technology companies, we just couldn't resist. Maybe next year this will no longer apply. However, in the mean time we encouraging designers to start charge a premium to clients who insist on supporting IE6. Just twitter with. "I pledge to charge a premium for IE6 work! #premium4ie6pledge"

  • Microsoft Windows
  • Computing
  • FTP clients
  • Internet Explorer
  • RSS aggregators
  • Windows XP
  • Internet Explorer 6
  • Internet Explorer 5
  • Mozilla Firefox
  • Google Chrome
  • web browser
  • Politics
  • stable IE7
  • Google
  • Government of Canada
  • Microsoft Corporation
  • JavaScript
  • Technology
  • Microsoft
  • Google Inc.

Section: 

Topic: 

Comments

IE6 holding back CLF WET 2.3

Hi Mike,

Today I was looking at some of the defect tracking for some of the new CLF WET 2.3 functions.

http://tbs-sct.ircan-rican.gc.ca/projects/gcwww-dialog/issues?set_filter...

I see complaints about functionality not working in IE6. Last year we had a discussion about IE6 in government through the Ottawa UX mailing list. Some people at that time claimed that the government was no longer supporting IE6, but based on what I saw today, it may actually be holding back the release of WET 2.3.

I know you are involved with this WET project somewhat so wanted to ask what you think. Do you think we still be supporting IE6 on government websites this time next year?

Thx

When will it finally die?

According to Wikipedia, it's officially supported by Microsoft till April 8, 2014. But with Microsoft actively encouraging folks to upgrade I'm hoping that all departments have finally seen the light.

I don't know about the official debates however and which departments are still holding out.  I believe that PWGSC has finally made the move away from IE6, at least in the National Capital Region.  

Next year at this time we'll be looking at WET 2.4 however, as there's supposed to be a 6 month release cycle. I do think they'd have trouble maintaining the requirement at the end of 2012, but I was shocked that there were departments officially supporting it in 2010, so I may not be a good judge.  

I have no inside information about it however.

Add new comment