When Microsoft announced that IE8 passed Acid2 on an internal build, I was very suspicious when they started talking of "IE8 standards mode". "Uh, oh. What is this?", I asked, and how does it apply to web standards.
Turns out, it is a proprietary "flag" which must be inserted into your web page markup to trigger this "IE8 standards mode" which, of course, makes that part of your page invalid. This flag is not set by the Acid2 test so...guess what my friends...IE8 does not pass Acid2!
However, the version of IE8 that will be released will not pass Acid2 as it will require pages to specifically request to be rendered in IE8 standards mode, and Acid2 does not request this.
More deception by Microsoft.
I suspect, without any
I suspect, without any evidence to lend credence, that MSFT has a serious issue with backward compatibility. We have standards and quirks mode now, and I'll bet IE8 needs yet another switched mode to avoid sending IE7 and IE6 renderings into the crapper.
Maybe IE8 has gotten hasLayout tamed and brought more into line with the W3's block formatting context. That would make IE8 act more like a modern browser. All those pages coded using IE≤6's buggy behavior would then break an IE8 standards compliant rendering, as they do in modern browsers.
Wikipedia is not a reliable
Wikipedia is not a reliable source and a pre-release version is nothing to make judgements upon. At this time its not reasonable to accuse Microsoft of anything.
Quote: Wikipedia is not a
Wikipedia is not a reliable source
As Acid test is not to taken as an indicator that a browser performs to the Standards.
I see the Acid2 test as one of those misleading little exercises that have people believing that it's more than it is.
In order for IE8 to render
From lead IE developer Chris Wilson:In order for IE8 to render Acid2, it must be triggered by an inserted meta tag.
The standards mode trigger is likely a META tag;
*sigh* I don't know what
I don't know what that source is, but you haven't even included the full quote and you've somehow changed a "likely" and an "I can't remember" into a "must".
Lachy: sorry, splitting attention in multiple directions. The standards mode trigger is likely a META tag; I can't remember exactly what we landed on. We'd been getting advice from a number of web developers privately on what they thought would work best in their workflow.
At this rate you're destroying your own credibility and you'll end up with as bad a reputation for spin as M$
My first post said there
My first post said there MUST be a "flag" of some sort.
My last post showed the flag LIKELY will be a meta tag.
In any case, there MUST be a flag for this.
How does that hurt my credibility? What did I say wrong?
My "sources" are the Microsoft IEBlog and the W3C Working Group and Wikipedia, including links. Good enough for you?
btw, if you bothered to read the links, you would notice the posters were Chris Wilson of Microsoft, and Hixie from the W3C, plus other W3C members.
I just followed one of the links in your footer drhowarddrfine! I liked this bit, how interesting...
"Conspiracy theorists have suggested that this (IE being so buggy) is because if browsers become too good, people will make web applications instead of desktop programs. If they were written using syntax that worked in all browsers, they would no longer be tied to using one operating system. Microsoft Windows would no longer be needed."