Email not displaying correctly? View it in your browser.

SitePoint Tech Times

Issue 235: April 7th, 2009  Tips, Tricks, News and Reviews for Web Coders


Raena Jackson ArmitageJust about every web developer I know becomes excited about a new browser version, and before long, we all start considering when it's time to stop worrying about the old version. This is especially obvious with Internet Explorer -- now that IE8 is out, many of us are wondering whether it's safe to stop supporting IE6.

As tempting as that seems, for a lot of us it's simply impractical to exclude this browser just yet -- in fact, since some people are forced to continue using it in the workplace, it's really an issue of accessibility. In this week's Tech Times Andrew discusses ways to keep treating IE6 nicely. More on that soon.

Meanwhile, we were finally able to reveal the total amount raised in our 5-for-1 Bushfire Appeal sale. As SitePoint's General Manager, Luke Cuthbertson, reported, the sale raised an amazing A$315,231.67 to help those affected by the Victorian bushfires in February. That's an astonishing sum of cash. So thank-you for your help -- those of you who spread the word, posted on Twitter, put it in your blogs, and bought books to make this appeal so successful. I'm sure I speak for all of us when I say how grateful we are to have seen the SitePoint community come together like this.


Support for IE6: It's All About Accessibility

by Andrew Tetlaw

With the release of IE8, there's excitement in the air about ending support for IE6. Will 2009 be the year in which everyone can drop IE6 support for good?

You've probably seen the anti-IE6 campaigns (Stop IE6, Bring Down IE6, End 6); some are well-intentioned like Browser Upgrade Information, while others have all the subtlety of a witch hunt, like the Shockingly Big IE6 Warning plugin for Wordpress. Before we all decide to burn IE6 users at the stake, I think we need to gain some perspective about who's still using IE6 and why. Here's an anecdote I can offer that will hopefully convince you that IE6 users are not an amorphous cloud of faceless evil.

In a previous job I worked for an architectural company, developing their intranet and web site. With regards to IT policy this company is far from conservative, often researching new technology with a view to improving their core product: excellent design. A few years ago, just before IE7 was released, the company made the decision to purchase a feature-filled, web-based project management and accounting system. It would considerably improve project management across the company -- but was only compatible with IE6.

Compatibility with IE7 was promised, but only delivered at the end of 2008. The IT manager has avoided upgrading the company to IE7, opting to wait for IE8. Luckily -- thanks to some clear-headed thinking on Microsoft's part -- IE8 can behave as IE7, so they'll be able to upgrade to IE8 and use the IE7 mode for their intranet. They have over 200 employees and only a small number of IT staff to manage the upgrade. It will probably happen this year, 2009.

You may be wondering why they've chosen to stay with Internet Explorer, rather than installing another browser for their everyday web browsing. The company uses Windows roaming profiles; this allows the architects to use any workstation in the company as they move between project teams -- sometimes between offices in different states. Windows group policy features are also used to manage employee credentials, permissions, and software settings more efficiently. Internet Explorer supports both of these tools very well, unlike other browsers. Why install a second browser that would only increase the workload of the small but efficient IT support team?

The architects at this company would be unable to act if presented with a message that their browser software should be upgraded. Such a message would be little more that an annoyance, or worse if their access to a site was restricted. It's an accessibility issue.

IE6 is still averaging around 20% of web traffic, so preventing IE6 users from accessing your web site is the wrong approach to take. I'm doubtful whether messages encouraging them to update their browser is going to help either. It's also inadvisable to simply stop testing in IE6. A rational approach is needed, one that considers what percentage of your sites' visitors use IE6, and what experience you should provide for them.

If you think you're using all that CSS has to offer, think again!

Don't be left behind!

Conditional Comments: Workarounds for IE6

Conditional comments are the best way to control the experience of your IE6 users. At the very least, IE6 users should be able to view your content. Using the confusingly named "downlevel-revealed" conditional comments you can hide all CSS from IE6 (and earlier versions), revealing only unstyled content:

<!--[if gte IE 7]><!-->
  <link rel="stylesheet" type="text/css" 

This is a similar approach to using @import to hide CSS from Netscape Navigator 4. CSS support in NN4 was broken and could crash the browser, which justified that drastic approach; IE6 is far more capable than NN4. The second option is to make a separate, simple but usable layout for IE6. For example, if your site's layout has multiple columns, make a single column layout for IE6. IE6 is served a special style sheet, while all other browsers are served the standard style sheet:

<!--[if gte IE 7]><!-->
  <link rel="stylesheet" type="text/css" 
<!--[if lt IE 7]>
  <link rel="stylesheet" type="text/css" 

The third option is to serve up the standard layout to IE6, but add a few fixes here and there, so that there may be some differences in the IE6 version. All browsers except IE6 are served the standard style sheet, while IE6 is served the standard style sheet plus the special IE6 style sheet. Using the cascade the special style sheet overrides some of the standard style rules to fix IE6 problems:

<link rel="stylesheet" type="text/css" 
<!--[if lt IE 7]>
  <link rel="stylesheet" type="text/css" 

An alternative approach, if the above is unsuited to your method of managing styles, is to use conditional comments to modify the body tag, like so:

<!--[if gte IE 7]><!-->
<!--[if lt IE 7]>
  <body class="ie6">

By doing the above, you simply preface a style rule selector with the class selector ".ie6" to make an IE6-only rule.

Whatever you choose to do, it has to make sense for your site. Research how many IE6 users visit your site and try to find out who they are. Some excellent articles have been written recently about how to deal with IE6:

So how will you deal with IE6? Add your comments to the blog entry:

Andrew Tetlaw Web Tech Blog: Technically Speaking
by Andrew Tetlaw

Support for IE6: It's all About Accessibility

We'll be back next week for another Tech Times.

Raena Jackson Armitage
Technical Editor, SitePoint

Latest Release

Sexy Web Design

Sexy Web Design Book Cover

Tell me more..

Free Book Samples

Sexy Web Design
Simply SQL
Simply JavaScript
The Principles Of Successful Freelancing

New Technical Articles

Six Easy Steps to Start Selling Online with OXID eShop

Vikram VaswaniThe sophistication of modern ecommerce solutions has improved to the point that you can set up and run an online store with minimal fuss. This ease of use is a boon to small and medium-sized merchants. In this article Vikram shows you how easy it is to setup an online shop using the OXID eShop software.

Full Story...

 Techy Forum Threads

 More Techy Blog Entries

Website Revenue Strategies

How to Sell Statistics to Clients

Web Design

Alkaline by Litmus: Windows Browser Testing for Mac Users


SitePoint Podcast #12: 41 Shades of Blue

Help Your Friends Out

People you care about can benefit from the wealth of information on new and maturing technologies available on the Internet. Help them learn how to do it by forwarding them this issue of the Tech Times!

Send this to a friend

Follow us on Twitter


You are subscribed as:

Unsubscribe from this list.
Manage your subscriptions.
View the newsletter archives.

Mailing Address:
48 Cambridge St, Collingwood, VIC, 3066 AU

Phone: +61 3 9090 8200

Back to the archives

Newsletter signup

Design, coding, community or marketing? Select the right newsletters right for your needs...