Colourgarden

jardin de coleur

Archive for August, 2009

The campaign to rid the world of Internet Explorer 6 (about time too!)

It’s been one of those things over the years, like fuel prices or video refereeing in football. We all moan about it but, in true British spirit, we do nothing about it. The horror show that is the Internet Explorer 6 browser has long been the bane of web developers everywhere but finally there is a group of people taking a stand (yes, they’re American) to rid the world of the IE6 plague.

Chances are if you’re reading this you will already know something about IE6 but for those of you who don’t then here is a brief history and a list of reasons why us web developers hate it so much.

Way back when (around the turn of the millenium) Microsoft had seen off the challenge of Netscape Navigator and had a near 100% share of the internet browser market and, as such, did pretty much whatever they wanted in terms of adhering to web standards. This meant that a piece of perfectly written CSS would often render incorrectly and a hack would be required to rectify the error. This care-free attitude from MS continued for several years and culminated in the launch of IE6 in 2001. At this point in time, everything was fairly rosy in the world of web development as sites were built to IE6 specifications as it was the predominant browser.

For all these years, Microsoft ignored web development standards to the detriment of future web users everywhere. A rather crude example in Lehman’s terms would be a car manufacturer changing round the pedals on a car so the accelerator is the brake and the brake is the accelerator. The accepted pedal structure is not written in a rulebook (as far as I know) but would cause havoc for drivers were it not to be adhered to. Obviously car manufacturers have a lot of competition in their market, unlike IE6 at the time, but you get the general idea.

It isn’t just small display issues for IE6 either. Blind users who may be using a screen reader browser (which ‘speaks’ out content on a website instead of a visual display) will not be able to use a large amount of websites (because they were designed to the specification of IE6) so it could be argued that, by ignoring recognised web standards for so many years, Microsoft has discriminated against disabled users.

2004 saw the launch of Mozilla Firefox and, as it became increasingly popular amongst internet users for, as well as other things, tabbed browsing and useful add-ons, finally Microsoft’s domination was beginning to be challenged. The purists at Mozilla had paid attention to web standards and this meant that all of a sudden a web developer, as well as a regular user, would find that websites would look different in Firefox to IE6. This is where the issues with IE6 started to become obvious to the wider web development community.

Microsoft now had a problem. Firefox was eating into their market share at a rapid rate but they couldn’t completely re-write their web browser to adhere to web standards as most of the websites on the internet are designed to display in their abominable creation – IE6.

And so we fast-forward to the current day. Microsoft have released versions 7 and 8 of their flagship web browser which, although marked improvements on IE6, still have gremlins and have the ongoing problem of plastering over their predecessor’s mistakes.

Fortunately, the internet (and websites) are now getting to the stage where IE6 is no longer viewed as a primary browser but it still causes web developers untold problems with its querky bugs which can add large amounts of time to projects.

And this is where IE6 No More comes in to give the devil browser the final shove into the grave. Led by David from Weebly, the group has garnered a large amount of support from big industry firms such as Justin.tv and Reddit and has even started to get mainstream media attention which can only be good for the future of the internet. The idea is that web developers add a small piece of code to their webpage which, if a user visits using IE6, they will be shown a banner making them aware that they are using an outdated browser and recommending they upgrade. It is a simple idea but one that could, and hopefully will, prove to be immensely successful at encouraging users to consign IE6 to the tech-graveyard.

Another shot in the arm for the web browser community is the European Court ruling that Microsoft cannot bundle Internet Explorer with their upcoming operating system Windows 7. This means that, hopefully, more regular web users will gravitate away from IE.

In my view, this volunteer project is one of the most important groups for the short-term future of web development and, to show my support, I have added the IE6 No More banner on my website.

Do your bit too. If you are using IE6 then please please please upgrade to a web standards compliant browser like Firefox or Google Chrome. Hey, even if your using IE7 or IE8 move in with the good guys and ditch Microsoft.

Happy browsing.

Firefox 4.0: Are Mozilla jumping on the bandwagon?

The relentless Mozilla machine recently released some interesting first looks at the next version of their ground-breaking browser – Firefox 4.0.

While Firefox 3.5 is still causing waves in browser innovation circles following it’s release in June and Firefox as a whole reached the one billion (!) download mark last Friday (31st July), the Mozilla team aren’t resting on their laurels and are busying themselves to even further improve the best browser on the net and devour further chunks of Microsoft’s browser market share.

Taking a look at the screenshots posted of Firefox 4.0, I am very undecided what to think of the cosmetic changes to the browser window.

There is a more profound use of the Windows Aero styling which, whilst very pretty, instantly reminds of Internet Explorer which isn’t a road I think Mozilla should be going down! The forward/back buttons as well as others seem to have been ‘lifted’ from a mixture of Safari, IE and Chrome. Of course, the beauty of Firefox is that you can change themes to customise the look of your browser but first impressions are everything.

I am not strictly a fan of the tabs at the very top of the window as featured in Safari and Chrome but the Firefox 4.0 ones are better implemented than any of their rivals as they don’t actually take up the whole of the title bar (a personal preference) with the nice addition of a home button on the left hand-side as well. I would very much like to see a choice offered in the next iteration to have tabs as they are on the current browser below the address bar area or at the top in the title bar. That way those of us stuck in our ways can keep to what we know and venture into unchartered territory when ready.

The whole of the address bar area for 4.0 has been simplified which seems to be the norm nowadays with hidden menus and less buttons to ‘get in the way’. The new combo button for stop, refresh and go is another streamlining feature which, although simple, is a classic Mozilla innovation. It changes colour and icon depending on what state the page is in (loading, loaded or new address being typed) and, lets face it, you can’t use all three actions at once so why waste the space with the icons?

The bookmarks button is clear and concise – a common flaw/annoyance in many modern browsers but the star icon in the address bar remains for quick bookmarking.

The new 4.0 concepts seem very much ‘less is more’ – still packed with features but cutting down on the clutter. Whether this means basic functions will be harder to find remains to be seen and whether Firefox should be ‘copying’ the models of Safari and Chrome by reducing the instant use of common features is debatable.

Of course, these opinions are all conjecture as the screenshots posted by Mozilla are very early designs and I’m sure the final version will differ drastically from some of the visuals but I’m hoping Mozilla stick to their guns and don’t jump on the bandwagon of simplicity too much. Maybe just follow behind on their push bike with a smug grin.

The real test for me will be the increased performance gains promised by the team. Loading times for Firefox still lag behind Safari and high memory usage issues still linger so lets hope these points are not overlooked in favour of wholesale changes to the cosmetics of the browser.

Watch this space.

Back to top