Eli Simpson

To IE or not to IE, that is the question

Yesterday I noticed that my site design was corrupted in IE 7, a symptom of the * html CSS hacks I was using to fix bugs in IE 5 and 6. IE 7 has fixed the parser bugs that made the hacks work, but didn’t fix all the problems in its CSS support that web developers use the hacks to fix, specifically its strange proprietary hasLayout property which causes all sorts of problems with even the simplest CSS designs.

In contemplating how to resolve the issue, I considered removing all hacks from the site and letting IE get its just deserts. This is my personal site and unlike my professional work, I’m under no obligation to spend my valuable time fixing issues with Microsoft’s primitive browsers, market share not withstanding. I must admit the temptation was very strong to punish IE users for continuing to use the insecure, buggy browser that causes me so much frustration in my professional life.

In the end, I (reluctantly) decided to continue to support IE, and took the approach of simplifying my design somewhat to need fewer hacks in first place, which is probably a good thing. I still may end up implementing some IE-only punishment in the future, such as an ad to download Firefox, Opera, Safari, or any of the other much better browsers on the market.

One Comment

Thanks for the useful info. It’s so interesting

  • Comment by JamesD

Leave a Reply