But the crappy intranet sites etc that are coded specifically to IE6 or IE7's quirks *won't* go away (as that's the whole reason why MS are doing this), so no, the meta tag (and the associated rendering engine) will stay. If they're freezing rendering unless you opt-in because corporates won't update the sites now, what makes you think that they will ever update the sites?
That's the whole idea. That they *won't* have to update their intranet application to account for a new IE rendering engine. And for an intranet application, and such like, web standards and semantics is not an issue. It's an application, it runs on the IE engine and it works.
And because of the delay and the meta-tag, more developers will have grown complacent and lazy (coding for just that rendering engine*), and so the number of sites that will 'break' will have increased.
Then they're made by non-professional developers. Which is how most sites are made anyway. Webdevelopers that cares about clean coding, semantics and webstandards are a minority. Most of the web is allready "broken". There's tagsoup and hacks all over the place. I can't see how this tag will change that.
******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
