2008 October — Chaotic Neutrality — Internet Marketing, Business, and Technology Blog by Greg Picarello

October 2008


I have recently started tinkering around with Microsoft Internet Explorer 8 Beta (IE 8) and noticed that the way it renders various CSS items has changes since IE7. I’m not sure whether some of these changes are due to bugs since it is in beta or whether it is due to Microsoft trying to better adhere to CSS standards (or some combination of both), but either way this perpetuates a problem for web developers who now must create new hacks for another broken version of Internet Explorer.

One problem I quickly noticed was that the navigation of a site I was working on was not displaying properly due to some bug with the way IE8 renders CSS (the navigation worked properly in Firefox, Opera, Safari, etc.).

Broken Menu in IE8

Example of Broken Menu in IE8

I quickly started to do research on IE8 beta and potential bugs, but could not find anything concrete. Instead, what I did find was that the geniuses at Microsoft decided to add support for a special META tag that IE8 will recognize and use to control the CSS standards and rendering model used for a specific page. For instance, I could add a META tag to tell IE8 to use the CSS model from Internet Explorer 7 to render my current page — thus removing the need for another set of hacks (but at what cost?).

I decided to give this a whirl and try that same navigation item using IE7’s CSS model. I added the following line to to the top of my section and tested the results:

<meta http-equiv=”X-UA-Compatible” content=”IE=7″ />

The following example was the result of the change in IE8:

Example of Now Working Menu in IE8 due to X-UA-Compatible META tag usage

Success! No need for new hacks or figuring out what was broken with IE8.

However, the problem is that this has the potential to retard web design in the sense that any page that uses this meta tag will be forever using an old deprecated method of rendering CSS. It freezes time, in a sense, for any pages that use this and makes an easy and lazy way to fix CSS bugs in old browsers without the need to understand or move forward with CSS usage and new methods and models.

Personally, I like the ability to trick IE into using the proper CSS model to make a page work. But, even though I’m not a web designer, I can see this creating problems down the road if designers do not work at making their pages display without the use of hacks and other workarounds — even if they are introduced and supported by Microsoft, itself.

Last week, I was forwarded a blog post on the Google Webmaster Central Blog about the use of URL rewritten URLs (for your dynamic querystring driven pages).

After having read the article and being asked a couple questions from friends and colleagues, I responded with the following:

My belief from both a SEO and Usability perspective is that…

  • URL Rewrites are good
    • SEO – it gives a place to use keywords (which in the past has been useful) and have more meaningful URL structures other than index.html with a bunch of querystring garbage attached.
    • Usability – querystring driven URLs are ‘ugly’ and take away from the user experience. I’m more likely to remember http://www.mysite.com/stuff/ than http://www.mysite.com/?id=7&content=stuff

Personally, I think Google’s message about URL Rewrites is absurd. I would also not act on this at this point in time since it is extremely new and there is no information to suggests need for imminent change. TONS of sites use URL Rewrites and it would be a major major major shift to move away from that.

In fact, it is highly likely that the blog that is reporting this change in Google thinking http://googlewebmastercentral.blogspot.com/2008/09/dynamic-urls-vs-static-urls.html ostensibly is using URL rewrites.

Ha. Silly.