Linked by Thom Holwerda on Fri 25th Jan 2008 13:00 UTC, submitted by gonzo
"Internet Explorer 8 is going to be the most standards-compliant IE yet, but it's going about it in a way that has some people scratching their heads. With Internet Explorer 8, you have a choice in standards compliance modes. Sound oxymoronic? Shouldn't there be one standards mode by default? Heck, shouldn't the only mode be standards mode? Ah, idealism." Please note, however, that John Resig of Mozilla Corporation spotted something interesting: "Internet Explorer 8 will support DOCTYPE switching for new DOCTYPEs (like HTML5). This really does change any frustration that someone should have concerning the new meta tag. This means that you can write your web pages in a completely standards-based way (CSS, HTML5, JavaScript) and not have to use a single browser-centric tag in order to do so."
Permalink for comment 297903
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-03-30
I admit that Microsoft essentially cleans up the mess that they are themselves responsible for in the first place. But if this crude meta tag causes IE6/IE7 et al to be replaced by a more standards compliant browser (IE8) in the near future (due to better user acceptance since it doesn't break all pages), then I reckon it will serve us all in the end.
I agree, as someone who does a lot of web development, I'll take having to add one (stupid) tag at the top rather than having to write every webpage with ugly hacks so it will work with IE.
I wonder though, how will the transition work? I mean, I personally still check all of my webpages in IE6 and hack away to make sure they look decent there. There are still too many people browsing with it to ignore, and when you're making a webpage for a client and getting paid good money to do so, it would be a very bad idea to leave it rendering poorly in any browser with a significant chunk of the market. When the people who paid you to make it start getting complaints, they're not going to want to hear "Well, its not my fault, its really Microsoft's fault for making such a bad browser, and your client's fault for not updating to the newest version." Not if you like getting re-hired at least.
So, I'm resigned to having to develop my sites for buggy IE for at least a few more years. Siiiigh. (This is what happens when competition is stifled! If Microsoft had played fair, we'd never be in this mess in the first place! Bitter much? Hell yes)