‘html>body’ Will it get me fired?

I’ve been using the html>body tag for a while now. It easy, quick, standards compliant and gets me around the IE box model. The thing is… I WANT THE IE BOX MODEL. And so do many others that have got half a brain.

Okay. I’d better calm down and get over the fact that we’re getting screwed by Safari (no box model switch) because there’s a real chance that IE7 will screw everthing else up anyway as soon as it comes out. Futerproofing is a myth.

Yes, yes, I know. I could have been using ‘hacks’ that target dead browsers (IE 5+)only. However I’m not very convinced that that would be the right solution because I simply have no idea what the future holds. I must have been sick the day they had a ‘clairvoyancy’ class. 
The problem is two fold. One is that when you write CSS for other purposes than it’s original intention you will always stand a real chance of it backfiring on you.
The second is that each web client renders (x)HTML and CSS differently, whether both comply or not. We will always have to use some form of a work-a-round to get a document to render similarly across clients and platforms. Back to square one.

I understand the logic of forward thinking as it allows for compliant coding that may extend in to the future. The reality is that futerproofing is merely based on assumptions. Our best guess of which web standard will be upheld down the road. With each release of IE Microsoft has actually been pretty good in implementing the standards along with adding their own proprietary functionality.

So why worry? Well no matter how much care each vendor takes in compliance and standards interpretation, it will never be what you thought what it was going to be. And the odds are that I won’t be the only one that will end up retro fitting their web sites after Internet Explorer 7 is released. I won’t get fired but I’ll have some explaining to do, along with coming up with some new hacks.

Next entry: Poster blogs
Previous entry: Searching for validation