Internet Explorer — All the joys of having a tooth pulled



Microsoft never ceases to amaze me. Since I build websites (my own and a few others), it is important to me that the site look the same in every browser (well, at least all the major ones). Thus, the fact that IE6 requires its own styles is a pain that I (and every other website developer) could do without. So, when I read that IE7 was “standards compliant” I thought that I could use the same styles that I use for Opera, Firefox and Safari. Silly, naive me. I didn’t research it out enough and simply took the word of some Microsoft apologists (had I known they were apologists for Microsoft I would have never listened), and thought I was done last Friday evening with recoding the mainpages of the site.

Today, I was informed that the pages didn’t float right in IE7 – not good. Thus, enduring the lengthy dial-up download of IE7, I (under duress – but I have to check the pages) then installed it on my wife’s computer. Sure enough – none of the floats were correct. In fact, it had the exact same problems as IE6, just in different directions. Joy. Now I had to have a second IE stylesheet to fix the problems of IE7, and I had to hack a fix for the articles section on every page that has articles.

However, it is done, and all without anesthetic (it would have felt better if I had had a tooth pulled). It does display (mostly) correctly, but I hated having to do it. Once again, Microsoft has proved that they don’t know what their doing.

Have I mentioned that I hate Microsoft products?


One Response to “Internet Explorer — All the joys of having a tooth pulled”

  1. ckm Says:

    I don’t know if you read slashdot at all, but there was a discussion today about IE 8 and how it may not be standards compliant. But I thought this comment by Slashdot user Myopic was particularly insightful:

    I just want to point out that these ongoing shenanigans show that IE is not a web browser. The whole world (including Microsoft) got together and decided exactly what a “web page” is and wrote it down in very clear specifications. So, anyone who writes a piece of software that renders a web page, as defined by those specifications, is a web browser. If you write software that does anything else, then that isn’t a web browser. Therefore, insofar as IE does not render web pages, it is not a web browser. So, if anyone complains that your documents don’t look right when they view them in IE, gently explain to them that your documents are web pages, and to view them the person needs a web browser, and IE isn’t a web browser.

    My goal as a web publisher is to stick to publicly accessible and publicly usable standards. When I choose to use a validating service to verify that my page/site is compliant with a set of standards, I should not have to then tweak my work for a single product. If more people would take myopic’s advice above, and point out the fact that IE is standards-broken, perhaps MS would be more motivated to fix their browser.

    I’m right there with you in your dislike for MS products as well! Keep pressing on! :)

Translate »