Accessibility Links

Search Blink-Design

Me, Myself and IE

The fun of trying to support Internet Explorer 6, don’t you just love it? For a long time we’ve bent over backwards with hacks and fixes to try and make designs look good in this silly browser. But now that IE 8 is on the loose I think we have more of an excuse than ever to just let it go.

Deciding on how much support to give IE 6 on the new blink-design website was an interesting decision. On one hand I may have visitors stuck in a corporate world that cannot upgrade or change browser but on the other hand I could easily have standards savvy experts scouring my code to see what kind of skill level I show.

Seeing as I’m not bound by any rules to support IE6 I decided I would make my site viewable and fairly acceptable in that browser (no massive faults such as float drops etc) but I really wouldn’t care about the little tweaks like margins, padding and other effects. This has opened me up to using far more CSS selectors, such as attributes, child and adjacent and writing my code has been so much more satisfying. I really hate adding a class or ID just so IE6 can use it.

Let’s take a look

Image Image

Now when you look at the home page in a side-by-side comparison it doesn’t look terrible but the devil is in the details.

For instance the toolbox has no fancy effects at all, it merely slides down. The search bar is totally unstyled as I’m using attribute selectors to target the different fields and finally the nav bar doesn’t have the location arrow as I couldn’t be bothered to use a non-transparent image for IE6.

The key here is that users of this browser can still use my site just fine and can read everything I have to say but they just get less of an experience. Working this way has probably saved me at least 2 hours in tweaking and also kept my pages lighter as I’ve dropped needless classes.

I think that if you have got the luxury then this is the way to proceed when dealing with IE6 and it’s worth convincing potential clients that they don’t need an identical website experience in a browser that is nearly 9 years old.

It’s just not feasible or fun.

Posted on Tuesday, April 14th 2009 and there are 14 comments

Categories: Site, Web Stuff

14 Comments

Contribute

Fields marked with * are required. Your email will not be shown.

  • Please enter the word you see in the image below: