IE8 Will Be Standards-Compliant By Default 383
A number of readers wrote in to make sure we know about Microsoft's change of heart regarding IE8. The new version of the dominant browser will render in full standards mode by default. Developers wishing to use quirks mode for IE6- and IE7-compatible rendering will have to opt in explicitly. We've previously discussed IE8's render mode a few times. Perhaps Opera's complaint to the EU or the EU's record antitrust fine had something to do with Redmond's about-face.
Correct link (Score:5, Informative)
Re:I don't care about IE at all (Score:5, Informative)
Re:Huge assumption in the title (Score:5, Informative)
+1 Informative (Score:2, Informative)
If you moderate in a thread and then post in it afterwards, all moderation will be erased. This happens even if you are posting anonymously.
Re:Put it all on Silverlight!?! (Score:3, Informative)
Re:Huge assumption in the title (Score:4, Informative)
Re:Windows Versions? (Score:2, Informative)
That link is from 2004.
Re:Question (Score:3, Informative)
Re:I don't care about IE at all (Score:5, Informative)
Well, since the link you provide is largely question marks for the Webkit based browsers, that's hard to say. Also, the comparison you link to is missing a lot of standards where Firefox is a bit behind. These include:
That is not to say Firefox is necessarily behind other browser for standards compliance in general. No one with a clue would cite the Acid tests as proof of anything in that regard, but it does indicate that the link you provide is not particularly strong evidence one way or another. The whole question is probably too vague to be answered. There are a lot of Web standards and what really matters is which ones are most universally supported and what functionality cannot be used because of lacking support in one browser or another.
In summary, I reject your assertion, not because I'm convinced you're wrong, but because you haven't provided enough evidence to support it and there is significant contradictory evidence (cited above).
Re:Hmmmm (Score:2, Informative)
Re:I don't care about IE at all (Score:5, Informative)
I disagree. At my last employer I used OmniWeb for a while (a very niche browser). Most of the Web UI developers used Firefox, but a couple used Konquerer. A few used Safari. A few used Camino. A few used Opera. Regardless of what you used, when you found a bug, you tested it with a couple of other browsers and if the remote Windows box was available (or you had an emulator running), you tested it on multiple browsers and multiple platforms.
The upshot of all of this was, when a bug was listed, it was pretty easy to see which bugs were specific to a given browser. Bugs that appeared in some version of IE, but in no other browser at all, were by far the most common occurrence. Realistically our approach boiled down to, "write to standards; then hack for IE. " Make no mistake, we did not code for some other browser then try to make it work on every one, because that was not needed for the most part. We were programmatically generating Web pages and interfaces from XML data and a couple of databases. For the vast majority of the time, all browsers but IE were close enough to the standards we used (HTML3, CSS2, XHTML) so that there were no discrepancies when tested.
Re:This Will Cost MS Dearly (Score:5, Informative)
You must not have read the press release [microsoft.com]!
They aren't putting their neck on the line... it's already there. :)
Acid2 is now obsolete! (Score:3, Informative)
I suppose this is why they already designed Acid3. [webstandards.org] Hint: Firefox 2 scores 50/100.
Improved standards isn't the story here (Score:5, Informative)
The real story here is that "Developers wishing to use quirks mode for IE6- and IE7-compatible rendering will have to opt in explicitly."
If you've been following any of the design / developer blogs and community response about this, you'll know that in a previous plan [alistapart.com], all web pages would render in IE7 standards mode unless the developer inserted a specific meta tag
into each web page of a site. (For the truly avant garde, one could set the content to "edge", which would tell IE to render in the most current standards compliant version available). The outcry was that while it was clear that IE was making progress in standards, in order to take advantage of those improvements, developers were being asked to touch each page of their sites and tell IE to use its more standards compliant mode. That discussion is what was at play here.Re:Huge assumption in the title (Score:3, Informative)
Acid3 (Score:5, Informative)
Firefox3 nightly from March 3rd: 66/100. (Second closest to the reference rendering.)
Safari 3.0.4: 39/100.
Opera 9.26: 46/100. (Looked the least like the reference rendering though.)
Webkit nightly from March 4th: 87/100. (It also looked the closest to the reference rendering.)
Re:+1 Informative (Score:3, Informative)
Re:I don't care about IE at all (Score:3, Informative)
Re:/.: Giving proprietors a pass and vapor = real. (Score:3, Informative)
Re:Improved standards isn't the story here (Score:3, Informative)
Old web pages will not have a DOCTYPE. If they don't have a DOCTYPE, IE 8 will render them using quirks mode. They will work exactly the same.
As a Web Developer, by including a strict doctype at the top of your current IE6/7 page, you are promising to be standards compliant. You shouldn't be ignoring standards and at the same time promising to browsers that you comply with standards.
If your strict IE6/7 junk doesn't render in IE8, then how is it currently working with firefox/opera etc.
If a developer cares so little about other browsers or doing things correctly, they deserve to have to update hundreds or web pages.
Re:I don't care about IE at all (Score:4, Informative)
That aside, I think supporting an open web is worth it.
/Mike
Re:Huge assumption in the title (Score:5, Informative)
When you get to the should / should not stuff, it comes down to in most cases you really want to listen to it, but there tend to be specific cases (say, embedded devices) where it really doesn't make sense to follow the normal behavior. Generally, if you run into one of those cases, it tends to be obvious that deviating from the spec is the right thing to do.
The optional and recommended stuff tends to be things that really depend on the specific product and shouldn't be forced.
Making things more strict would be a bad thing and make people break the standards more. The current setup acknowledges that different implementations have different needs and does a good job of accommodating.
Re:Improved standards isn't the story here (Score:3, Informative)
Look closer. The meta tag with http-equiv argument means that the browser should treat it as if it was an HTTP header field. You can accomplish the same effect by configuring the web server to include a "X-UA-Compatible: IE=7" header. On Apache it only takes a single line in the configuration file to add a static header to every page. I imagine the same is possible on IIS.
Re:I don't care about IE at all (Score:4, Informative)
Hence the fact that Wine runs it is moot.
/mike
Re:They also said Windows NT was POSIX compliant. (Score:3, Informative)
None of the mainstream Unix vendors actually did this, so most Unix code was written on the assumption that very little was not implemented. Windows, OTOH, returned ERROR_NOT_IMPLEMENTED everywhere it could. With fairly predictable results.
Re:Improved standards isn't the story here (Score:3, Informative)
Note that this situation is slightly different from the problems people experienced when upgrading from IE6 to IE7. If your site looks correct in IE7 but is broken in IE8, all you have to do is add a simple META tag. Yes, it's more obnoxious in the short term than if IE7 compatibility were the default, but I really don't expect most sites to have a problem with it.
Re:Huge assumption in the title (Score:3, Informative)