Over the weekend, as I was doing some work and testing some code, I asked myself a question that I constantly ask myself. Why am I still taking the time to code IE6 specific fixes and hacks into my work? I do all of my work on a MacBook Pro, downside number one. I used to have a PC desktop as well, and still do, but I simply do not have the room to setup my old school CRT.
Now I know part of my problem is that if I wish to develop completely, not properly, I need a PC to check my work on as well. This would make life easier and keep me from spending the extra time coding specifically for IE6. Through Google Analytics I still see that a majority of my works audience still use IE6 as a dominant browser, but its now a thin margin. It seems like many places “that matter” according to my demographic are making the transition away from IE6 and moving into more standards compliant browsers.
So I have a few questions I hope some of you can answer:
- Do you still place IE hacks/fixes in your code?
- How much time of your development cycle is spent doing this?
- Does the majority of your demographics still show IE6 as the dominant browser?
- When do you think you will stop coding for IE6?
Here are my answers:
- Yes I do, depending on the project. Trying to shy away from it at the moment.
- I usually leave this for last since it is still a real trial and error aspect for me. I spend a lot of time on it to say the least and that bothers me. Does this make a less competent developer?
- Some sites yes but a majority of my sites and audience I build for have really moved on, there are other fish in the sea.
- I don’t really know. Lately I have felt like I can really start to ignore the IE6 market and focus on more compliant browsers. I’d really like to take a que from major market players but I think that might be 2-3 years off at the moment.
So, does my lack of interest in learning more IE6 fixes and hacks make me less of a developer or does it help solidify the idea of moving forward as a good developer should? I know its important to remember the basics and all, but at what point is it ok to take IE6 off life support and let it die the peaceful death it needs to?
Text book answer: IE6 Still matters and will continue to matter far into the near future.
In a perfect world, we’ve collected all the hacks and work-arounds required to deploy the ultimate, cutting edge web site that every customer wants. In a slightly less than perfect world, we know the coolest framework that makes everything easy for us. In reality, I don’t have any answers, just questions. As you know, I am a big big fan of process and planning… Do you think it is possible to identify all the browser specific hacks and quirks that are required before beginning to develop? Perhaps this could be done somewhere between creating wireframes and beginning site development?
if websites would revert back to being text based, we wouldn’t have these problems!
</pseudopurist>
1) Yes, I still argue with IE6
2) Too much time.
3) Between 09/2007 - 05/2008 25% of my visitors use IE, 58% of them still use IE6. As much as I may not like it IE6 still has a stronger hold than Opera & Safari.
4) Hmmm.. When IE6 contributes less than 2% of my visitors?