What's so wrong with adding a tag that says "use IE8"?
Standards are a type of contract creating abstraction. If you develop to standards, you don't need to know, nor should you, what browser or version they are running.
This tag breaks that abstraction. It's white box rather than black box development.
And that usually ends in tears: when the browser version changes, when the browser brand changes (Opera, Safari, Firefox, etc). The tag starts to take responsibility away from web developers, to the browser developer, for crappy code. That engenders complacency and laziness. Neither of which is good for the developer or for the browser developer.
What happens when many people are relying on IE7 rendering and MS decide to stop supporting it? The web will still be 'broken'.
The issue of legacy will always be there. We are on the cusp of a mobile web and an XML web. I think being forward-thinking here is more important than backwards-compatibility (which is solved within the standards anyway). Thing big.
Sure we have numbers on the web now, but the prediction is that we will have double, if not more, on the web through mobile devices.
If we can get it right, now, as it should have been, it will solve the problems for the future. And due to the expected increase of numbers, the problems will be even bigger than now. A little bit of pain now (going standards) is worth it.
Kat "I believe in an XML world." ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
