Former e-government minister Tom Watson has tabled a string of Parliamentary Questions, asking various government departments what plans they have to upgrade their default web browser from Internet Explorer v6. The answers are starting to come in, and they aren’t pretty.
… no plans to change …
… in the process of reviewing the options… no decision as to which web browser the Department will update to or when any update might take place …
… currently reviewing our options …
… the upgrade to IE is planned to be completed prior to Microsoft ceasing to support IE6 …
But the most depressing response so far comes from the Ministry of Defence:
The Ministry of Defence (MOD) is currently implementing the Defence Information Infrastructure (Future) (DII(F)). DII(F) will, once delivered in full, incorporate around 140,000 terminals supporting some 300,000 users at over 2,000 defence sites worldwide, including on ships and deployed operations. DII currently uses Internet Explorer 6 and at the current time does not have a requirement to move to an updated version.
So maybe it’s worth running through precisely why it’s such a bad thing that government departments aren’t being systematically moved off IE6. It’s partly technical, partly design – but mostly, I think, it’s the symbolism of departments refusing to move forward.
On the technical front, IE6 has security holes that just aren’t being fixed. Analysts Secunia say there have been 10 security alerts in the last year; and that there are 21 unresolved problems. Now to be honest, day-to-day, this probably doesn’t amount to much more than a theoretical risk, but it’s a risk nonetheless.
Then there’s the design issues. Most web design these days is (or should be) based entirely on CSS, Cascading Style Sheets. And frankly, IE6’s handling of CSS is appalling. Ask any web designer, they’ll tell you the same story:
If you follow the W3C rules, designs will generally work perfectly (ish) first time on Firefox, Chrome, Safari, and in all fairness, IE8. Then you hold your breath, and test it in IE6… and goodness knows how it’ll come out. Things might be the wrong size, or in the wrong place, or might not be visible at all. The layout you spent weeks crafting could be a complete mess. You then have to spend ages bastardising your code, often breaking those W3C rules – and sometimes defying all logic! – to make it come out right, or near enough, in IE6. It takes time, it costs clients money, and it makes designers sad.
In reality, everyone in the industry knows this. We’ve been living with it for long enough, and we’ve all got our various workarounds. We factor the IE6 delay into our timescales. We know not to be too ambitious sometimes, ‘because it’ll never work in IE6’.
But the reason it’s such a sore point for us government hangers-on is that IE7 (released in October 2006) is free of charge, and Microsoft’s formally recommended course of action is to upgrade. Dammit, that’s what HM Government itself tells people to do. Yet departments are quite happily burying their heads in the sand – ignoring the sound technical, financial and qualitative reasons for upgrading.
They think doing nothing is the safe option. They’re wrong.