Standard storm

23 January 2008

First read this (although you probably have already):

Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8

Then take a look at these:

Broken (If you only read one of these, make it this one)
From Switches to Targets: A Standardista’s Journey
Has Internet Explorer Just Shot Itself in the Foot?
Predicting the Past
Not your father’s standards switch
The versioning switch is not a browser detect
Code Happy
Best Standards Support
In defense of version targeting
Standards mode is the new quirks mode
The Internet Explorer lock-in
Who loses out to X-UA-Compatible?
IE8 and the future of the web
Versioning, Compatibility and Standards (from the Safari/WebKit devs)

Needless to say I’m not sure if this concept of version targeting has gone down too well.

I’m firmly on the side of those saying this is a bad idea. It strikes me that this is Microsoft trying to push something that solves a problem specific to them (namely that IE6 was so bad that when IE7 came out lots of things broke) onto the shoulders of web developers. While it’s not particularly pragmatic to say, I think this is really not our problem and the proposed solution has all sorts of downsides; it breaks the concept of progressive enhancement, bloats rendering engines and slows the adoption of new html/css features in the IE userbase.

I also have the feeling that like the the strict doctype before it, in practice this won’t work anyway. Like all good developers, Microsoft are proposing a loophole in the form of setting the X-UA-Compatible tag to ‘IE=edge’, which means you just get the latest version of the IE engine (like you would right now). I can’t see anyone not using this, outside the Microsoft-only devs that got pissed off with IE7, so the whole concept becomes a bit of a red herring. In fact, one of the ways that this could be improved would be if it defaulted to this setting, so the default behaviour isn’t being changed – as Jeremy points out, it’s crazy that unless you tell IE8 to behave like IE8, it’ll behave like IE7; surely that’s not the default behaviour we want?

All that said, there is the kernel of a problem trying to be solved here; namely how to write CSS code (and we are talking just CSS, not HTML, as this discussion is all about presentation) that doesn’t break when newer browsers come out.

Here’s what I’m thinking would be a good way of fixing it: Firstly, with the release of IE8 bring in either a new doctype (‘Standard’?) or a meta tag that announces that this page is expecting a standard compliant renderer. IE8 apparently passes the ACID2 test so should hopefully be on par with the other major browsers, and this flag will prevent IE8 ‘breaking the web’ again from Microsoft’s point of view.

Next, we need to have some way going forward of coping with new advancements to CSS without effecting older browsers. I see two ways of tackling this (possibly in combination): 1) Add a ‘version’ attribute to the CSS link tag, and then browsers can alter their rendering based on this (which is a similar solution to the X-UA-Compatible one, but seems a more appropriate place to do it). 2) Add conditionals to CSS that can detect what features a browser has available. I see this second one working roughly like this:

/* if( text-shadow ) {
p {
text-shadow: 1px 1px 2px black;
color: white;
} */

You could then supply different CSS to browsers based on whether they supported a specific feature, and using the cascade supply ones that didn’t something else. I’ve wrapped it in comment tags so that any older browser that doesn’t understand the conditional will just ignore it; this is quite purposely like the IE-specific conditional comments tags, which I think are also a good solution to this problem (which already exist!) and would be good to have adopted by the other browser manufacturers.

Here’s hoping that this loud reaction will give Microsoft some pause in rolling this out; they look like they’re moving in the right direction with IE8 so I hope that don’t screw up on an issue like this.

Signup to receive the latest articles from de-online in your inbox:

Further reading:


I was talking recently with someone I know who works at a music media company. I say “media company” both to be purposefully vague but also because I struggle to think of a better term that encompasses the merging worlds of distribution, retail and promotion.

Day in, day out, they get...

High Wire

Releasing music is getting complicated, isn’t it? Once, you’d simply use huge factories dotted around the world to etch your record onto a small plastic disc, then use fleets of planes, trains and automobiles to get them into thousands of stores dotted around high streets hither and thither.

Now you just...


I have two main ways of getting to work. One way – my normal way – involves a slightly soulless walk, slightly mediocre coffee, and a slightly less crowded tube train at the end of it. The other way features rammed carriages but significantly better flat whites.

I was in the...

You Used To Call Me On My Cellphone

My first MP3 player was this terrible, brick-like contraption made by Nokia. I couldn’t afford a regular player, so to take part in the nascent digital music revolution I was forced to get something on a phone contract that also happened to play MP3s. I paid a big price, not...

I Want My MTV

You’ve watched Making A Murderer, haven’t you? And of course when I say watched I really mean binged, episode after episode flickering past in a haze of instant entertainment addiction. If you haven’t watched that show, you will almost certainly be familiar with the experience.

Making A Murderer – and its...