IE 8 Passes Acid2 Test

notamicrosoftlover writes to tell us Channel9 is reporting that Internet Explorer 8 has correctly rendered the Acid2 page in "standards mode". "With respect to standards and interoperability, our goal in developing Internet Explorer 8 is to support the right set of standards with excellent implementations and do so without breaking the existing web. This second goal refers to the lessons we learned during IE 7. IE7's CSS improvements made IE more compliant with some standards and less compatible with some sites on the web as they were coded. Many sites and developers have done special work to work well with IE6, mostly as a result of the evolution of the web and standards since 2001 and the level of support in the various versions of IE that pre-date many standards. We have a responsibility to respect the work that sites have already done to work with IE. We must deliver improved standards support and backwards compatibility so that IE8 (1) continues to work with the billions of pages on the web today that already work in IE6 and IE7 and (2) makes the development of the next billion pages, in an interoperable way, much easier. We'll blog more, and learn more, about this during the IE8 beta cycle." There's also a video interview regarding IE8 development on Channel9."

So let's geek this out

If it takes until version 8 to support Acid 2, or 2^3,
then, when Acid 3 comes out, we can expect conformance by IE27?

Re:So let's geek this out

You might note that only a couple browsers completely pass it. [wikipedia.org] Officially released web browsers that pass there is only Konqueror, Safari 2.02; firefox does not make the list. So ~97% of all browsers don't pass it.

Since you had to...

...google for how to take a screenshot on linux... I do not think I trust your findings... Ad hominem FTW!!!.. ;P ... j/k

Re:So let's geek this out

The real question is, how back-portable is the IE8 browser? If it only runs on Vista, it's not going to matter much.

Re:So let's geek this out

Hopefully, it's more than just:

if (url == acid2 test page)
    display jpg of correct acid2 rendering
else ...

Re:So let's geek this out

I find it something of a curious coincidence that as soon as Opera starts asking the EU to take legal action against MS and the little web developer revolt a while ago about the distinct lack of any information coming from the IE team regarding 8 that all of a sudden we have this "we'll be passing the acid2 test".

I can't help be slightly suspicious. I'll believe it when I see it.

Re:So let's geek this out

I can't help be slightly suspicious.

It explains why they've switched [microsoft.com] to the Word rendering engine for Outlook. The fewer places they're standards compliant, the better for their lockin.

Re:So let's geek this out

Actually it all happened when someone cornered Bill Gates about how the IE team hadn't been communicating like he had promised they would, and how they were behind in their deliverables.

I would have loved to be in the Room when the call came in.

"Please hold for Bill Gates."
--CRAP, what did I do now--
"Hey, Junior, why did you make me look like an ass in front of the whole world?"
"Ummm..."
"SHUT UP AND DON'T TALK. I just got out of an interview, and they asked me why you were are not communicating. Don't answer that. You know how I hate interviews. You also know how I hate looking like an ass. You also know I told the world we would release IE8 in early 2008. So what gives. Do I need to fire you all and rebrand a version of FireFox as IE8? Cause I'm this close to doing it. Its people like you who give this company a bad name. Now stop wasting my time, start communicating, and the next time we talk you had better have numbers on how many people are switching from IE7 to IE8. If not, please be aware that the next group guy you talk to here at Microsoft will be our security guards escorting you off property. Oh, and by the way, Channel 9 will be there in the morning. The marketing department will be there in the afternoon, and you have been registered in the company communication 101 classes that are offered the first week of every month in Redmond. I've already spoken to the trainer and she is looking forward to working with you each month for the next year. I also what you to be aware that all this work will not impact our deliver date of 1st Quarter 2008.
"Why are you still on the phone. I thought you had code to check in."
-click-

Lesson: Never make the richest guy in the world look like a liar. Especially if he is signing your paycheck.

Appropriate Tag

I think the holyshit tag would be appropriate here.

Re:Appropriate Tag

How cyclical: first there were tags... then there were people using tags for comments... I've seen tags that said 'dontcommentintags'... and now there are comments suggesting how to tag. :-)

Re:Appropriate Tag

Na. Don't forget it only passes when in standards compliance mode, which must be declaired in the doctype of the page. By default (most pages) IE will render in "quirks mode", which of course is the hellhole we all hate.

Only with standard DOCTYPE

To be fair, any page without a DOCTYPE is not compliant, and can't be rendered in a compliant way. Any page without a DOCTYPE is probably buggy in other ways too. Firefox has a quirks mode too, and tries to fix buggy pages. It identifies a buggy page the same way, by looking at the DOCTYPE.

Everybody is in a pickle when it comes to rendering broken HTML. The only solutions are to do the best you can, or display an error message rather than a page. Also, to be fair, most of this mess is indeed caused by Microsoft, but even they can't fix it in a day.

I think it would be nice if browsers continued to fix spaghetti, but also showed a message somewhere that indicated that the page was buggy. Not a pop-up or anything, but a small, unobtrusive icon that was green and happy for a good page, or red and frowny for a bad. If IE had this by default, I think there would be a lot less bad pages on the internet.

Would anyone mind if....

...so that IE8 (1) continues to work with the billions of pages on the web today that already work in IE6 and IE7

Would anyone mind if they had rewrite their web pages or at the very least, remove the code that checks for the version of IE and if it is IE in the first place? I wouldn't mind.

Cool.

I guess when Bill Gates asks what the hell is going on [slashdot.org], he gets results!

Re:Cool.

Between IE passing a strict CSS test and 3DRealms planning to release Duke Nukem Forever, I'm wondering what alternate universe I woke up in this morning.

I guess I'd better check Google's top execs for goatees again.

Oh crap. [google.com]

Good News/Bad News

Good News:
Web developers will finally be able to develop a page once, according to standards, and have it work on all major browser ...

Bad News:
... in the year 2012 (give or take a few years), when the percentage of web users using IE 5, 6 or 7 finally dips below 5%.

What, No Comments?

What have we seen recently?

The people behind the Phantom actually releasing a product
A Duke Nukem Forever teaser
Dell promoting Linux
IE8 passing Acid2

What's next?
Dogs living with cats??

So they've realized how untrusted they are...

Am I the only one who thinks it's hilarious how thorough the author is in proving that this is really true. There's a screenshot of the test, video, and even a screenshot of the checkin.

It's almost like think we don't trust them or something.

Remember kids...

... passing the Acid test doesn't mean the browser's perfect. From http://www.webstandards.org/action/acid2/guide/ [webstandards.org]

Everything that Acid2 tests is specified in a Web standard, but not all Web standards are tested. Acid2 does not guarantee conformance with any specification.

And, from what I've read before, it tests how browsers handle incorrect code [webstandards.org] as much as anything else--i.e., if it deals with errors correctly. I'd rather have it handle every bit of the spec correctly in the first place, and if it fails gracefully, that's nice too.

It'll also be nice it it handles transparent PNGs properly with nothing more than an <img> tag--like how IE/5 Mac did almost eight fucking years ago. [wikipedia.org] Here's how much progress they had made as of 6/2006. [slashdot.org] (Yeah, it's been a while, and maybe they've fixed that, but c'mon.... it was 2006!) Too bad they lined up the Mac guys against a wall and shot them, ensuring that it would take almost a decade to get that one feature into IE/Win.

Feel free to correct me if I've made any factual errors in this post.* Flame if you want, but nicely worded, verifiable responses are preferred and worth a lot more to readers in general.

* aside from the part about shooting the Mac team--I'm (pretty) sure that didn't happen.

Re:Remember kids...

It'll also be nice it it handles transparent PNGs properly with nothing more than an tag--like how IE/5 Mac did almost eight fucking years ago.

They finally did in IE7, released in November 2006.

And, from what I've read before, it tests how browsers handle incorrect code as much as anything else--i.e., if it deals with errors correctly.

That's not the only thing it tests, but proper error handling is critical for forward compatibility. A fully CSS2-compliant browser, when faced with CSS3, will see it as incorrect code. Ditto for an HTML4 browser looking at HTML5 or XHTML1. If there are well-specified ways to handle errors, and the browsers follow them, then you can predict what browsers will do if they don't support a particular feature.

Re:"standards mode"?

Standards mode is invoked when you specify a strict doctype in the page.

This IS out of the box support. Let's have less false assumptions and cheap shots at Microsoft, okay?

Re:any standard will do

So in other words, it will be standards compliant but at the same time render all the old crap that wasn't even close to standards compliant??? So what's the point?!!

Because different kinds of pages are rendered with different rendering engines. The rendering engine that handles all the ugly old hand-written crap is known as "quirks mode" and is full of all their weird kludges that make those pages readable. If the page has the right document type declaration [wikipedia.org], it uses a standards compliance mode. The problem with IE has always been that it didn't implement most of the HTML and CSS specs, so there was little to be gained by forcing it into standards compliance mode. In other words, standards compliance mode wasn't really standards compliant. It didn't help that clueless MS spokespeople would talk about somebody supporting "more CSS features", indicating a nasty lack of understanding of standards issues. Since the specs weren't supported on the #1 browser, there were effectively meaningless.

Apparently that's now changed, and that's a very good thing. Personally, I credit the fact that Gates has given up the role of "software architect" in order to spend more time on his philanthropy. When he left, he seemed to take a lot of organizational arrogance with him.

Somebody is going to point out that ACID2 is not that great an example of real world CSS usage. That's perfectly true (how often do you use CSS to make silly pictures?) but the mere fact that MS has made passing the test a priority indicates a shift in attitude that we should all applaud.

Re:Wonder how long

IE requires the user to turn on a special "standards mode" to correctly render STANDARD WEBSITES.

The concept of "standards mode" and "quirks mode" has been around for several years, and is implemented in IE6, IE7, Firefox, and Opera, and for all I know in Gecko as well. The user does not have to flip a switch. The developer has to put some code at the beginning to show that he knows what he's doing, usually in the form of an appropriate DOCTYPE.

Re:Dec 19?

Crazier things are happening *now*. I have a date tonight. With a girl! :3

Yes, ACID2 is broken - Server error

I noticed the same error on Konqueror 3.5.8, Opera 9.5a, & Firefox 3 on Linux, and on Opera 9.24 and Safari 3.04 on Windows -- all of which are supposed to pass the test.

Earlier today I tried to pull up the webstandards.org website, and couldn't. This got me thinking it might be a server problem.

I looked at the code for the test, and at one point it has an OBJECT where it tries to load the url, http://www.webstandards.org/404/ [webstandards.org]. That should fail, causing the browser to display the fallback content inside the OBJECT element instead.

Guess what? That URL is returning a 200 OK code instead of 404 Not Found, so the compliant browsers are doing what they're supposed to do and displaying the content of that page in a little rectangle with scroll bars, and hiding the fallback content that we would normally see.

When their webmaster fixes the server config, the various compliant browsers should start displaying it correctly again.