summaryrefslogtreecommitdiff
path: root/_posts/2009-08-19-should-you-still-support-ie-6.html
blob: 66ca564afd5c8d59a3feea2a747cba67ecd33694 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
---
layout: post
title: Should you still support IE 6?
tags:
- Design
- Loadacrap
status: publish
type: post
published: true
meta:
  _edit_last: '1'
---
Yea, that's right: I'm talking about <em>you-know-which browser</em>.
<h3>What is this IE 6 phenomenon anyway??</h3>
Internet Explorer 6 is the 8-year old Microsoft browser, it comes by default in Windows XP. There are already versions 7 and 8 for this browser. Version 6 is now extremely outdated as it doesn't offer the best experience and quality when visiting a website. Web standards have evolved since the time and so upgrade is extremely recommended for all users.

<!--more-->
<h3>Are you a designer? An aware one?</h3>
If you are, then you know that IE 6 is a PITA when it comes to designing a website or application. Its support for CSS 2 is not perfect and thus it causes a lot of frustration. In my case, it takes double the work (and money) to support websites in IE 6.
<h3>What about “those” clients? They only use IE 6!</h3>
If you have clients that still use IE 6, it really depends on what you wrote a contract for. If you promised to support it, well... there is nothing you can do. What you <em>can</em> do is prepare for the future.

Paul Boag said brilliantly:
<blockquote>The energy we are spending in dropping IE 6 should be used to make our clients realize the truth about IE 6, providing a <strong>lesser experience</strong>.</blockquote>
I agree 100% with Paul. We are being plain old silly by even considering tweaking what's good. Old browsers should have an experience of their own. In the end of it all, <strong>what matters most is the content</strong>.
<h3>So this means the problem is not the browser?</h3>
YES, the problem is NOT the browser. The problem is what people make of it, both designers and users. Designers have the responsibility to warn the user about the lesser experience and say how they can enjoy the full show. Splitting CSS apart and delivering them according to each browser's capabilities is key. If the full means upgrading, fine. Users will be able to choose now.

If they choose to upgrade, don't be a fool, go help the guy! You will score good points.