Acid3 Test Released. I Took Some Screen Captures. Lots of Fail.

Posted on by Rob Larsen

Screen Shots

These were done with browsercam, so the test may or may not have fully run its course by the time the 15 second delay was up. Still, it’s not like any of these browsers were close, so a few seconds isn’t going to save them if, in fact, they were cut off before the rendering was over.

As a note, I tried to do the Capture in Konqueror and it pretty much made Browsercam cry and/or vomit (“Do NOT Try The Capture Again!”) I’m going to log in shortly to see what the actual damage is.

[update]It’s a known bug and some commentors were gracious enough to take screen shots with updated versions.[/update]

Reference Rendering:

reference-rendering.png

And now the Fail parade:

Camino 1.51 Mac OS 10.5

camino-151-mac.png

Firefox 2 Mac OS 10.5

firefox-2-mac-105.png

Firefox 3 Mac OS 10.5

firefox-3-mac.png

Internet Explorer 6 Windows XP

ie-6-xp.png

Internet Explorer 7 Windows Vista

ie-7-vista.png

Internet Explorer 7 Windows XP

ie-7-xp.png

Firefox 2 Windows XP

firefox-2-xp.png

Firefox 3 Windows XP

firefox-3-xp.png

Safari 3 Mac OS 10.5

[update]as seen in the comments the latest build is now scoring 87/100[/update]

safari-3-105.png

[update]Sorry Opera! I had the capture, but forgot to post it in my rush to get out the door today[/update]

Opera 9.24 Windows Vista

opera-924-vista.png

Here’s Konqueror built from SVN 2008.03.06 (thanks to Ronald Hummelink and everyone else that sent in Konqueror captures)

acid3_konqueror_20080306.png

And here’s IE8 Beta:

ie8-acid3.png

Opera 9.5:

acid3-opera-95.jpg

Firefox 3 Beta 4 on Windows XP

firefox-3-beta-4-acid3.jpg

[update! 3-27-2008] As everyone now knows, we’ve had a winner in the race to pass Acid3. Congrats to the WebKit team

acid-3-passed.jpg

[update 2008.9.02 I added Google Chrome Screen shot]

Now, the press release:

Acid3: Putting Browser Makers on Notice, Again. – The Web Standards Project

Acid3: Putting Browser Makers on Notice, Again.

Released: 3 March 2008 | Author: The Web Standards Project

The Web Standards Project (WaSP) today announced the release of Acid3, the latest in a line of tests designed to expose flaws in the implementation of mature Web standards in Web browsers. By making sure their software adheres to the test, the creators of these products can be more confident that their software will display and function with Web pages correctly both now and with Web pages of the future.

The Acid3 Test is designed to test specifications for Web 2.0, and exposes potential flaws in implementations of the public ECMAScript 262 and W3C Document Object Model 2 standards. Collectively known as DOM Scripting, it is these technologies that enable advanced page interactivity and power many advanced web applications such as web-based email and online office applications.

As a series of 100 mini-tests, Acid3 has already been found to expose flaws in all tested browsers, including Internet Explorer, Firefox, Opera, and Safari. WaSP hopes that Acid3 will prove useful to browser makers during the development of future versions of their products.

WaSP has a history of such initiatives. In 1997, emeritus member Todd Fahrner, together with a group of crack Web developers dubbed the “CSS Samurai,” created an “Acid Test” that highlighted shortcomings in browser support for CSS. The Acid Test was instrumental in moving the industry much closer to the goal of consistent rendering of Web pages in different browsers. This was followed by Acid2 in 2005, designed to expose flaws in the implementation of mature Web standards such as HTML, CSS, and PNG. Acid3 builds on and extends this legacy to web applications in 2008.

Acid3 can be found online at http://www.webstandards.org/acid3/

52 thoughts on “Acid3 Test Released. I Took Some Screen Captures. Lots of Fail.”

  4. Yeah, as I mentioned in #2 Hixie wrote about that when unleashing acid3 on the world. I need to source a screen shot and update the post…

  8. “Where’s opera?”

    Runs off to edit the post…

    Right there at the bottom 🙂

    Sorry about missing it the first time around!

  9. Pingback: Web 2.0 Announcer

  13. I’m swamped today, but I’ll check out Opera 9.5 today if I get the chance. right now I’m working off of browsercam, but I’m more than happy to expand this beyond the walls of browsercam’s test suite if it’s possible for me to do so.

  16. As I mentioned (right before the screen shots start), unpatched, Acid3 kills Konqueror.

    It’s a known bug ( http://bugs.kde.org/show_bug.cgi?id=155451 )

    I don’t have access to a Linux machine running KDE ( outside of the one at Browsercam) at present, so I can’t do the test myself with a patched version. If anyone wants to contribute a screen shot of a patched version of Konqueror I’ll gladly post it.

  21. “legoman666 Says:

    I just ran it on FF3 beta 3 and got a 58/100.

    ?”

    deactivate adblock and run it again, at least it worked for me

  24. Wow, just more proof IE is the worst main stream web browser out there. I still don’t get why it’s still the most popular.

  25. Does anyone else find it problematic that the official “reference rendering” is not an image, but itself a HTML page? What if a browser fails the reference rendering — but in the same way it fails the Acid3 test?

    Theoretically a new web browser can be created in five minutes which passes the test: It renders any given web page to a blank white canvas. The Acid3 will “look exactly, pixel for pixel, like the reference rendering”, as the requirement reads.

  27. Gee, a very early beta (IE8) gets a low score… what a mark against it.

    Fizzycakes:

    It’s most popular because it’s the default browser for windows.

  32. For what its worth I got a score of 39/100 running Safari on an iPhone with 1.1.4 firmware. While very impressive, this is not terribly surprising since it is after all running pretty much the same Mac OS X and Safari (and webkit) code as on a Mac.

    Safari 3.0 under Mac OS X 10.4.11 also gets the same 39/100 score (as previously reported for Mac OS X 10.5).

    I also tried a Nokia N95 mobile phone but it completely failed to run the test. This was a surprise since it is supposed to use webkit (like Safari), it failed due to a lack of Javascript support.

    A Palm TX running the Blazer browser seemed to get a bit further than the Nokia but also failed to score anything.

    Finally, just for laughs I tried Internet Explorer 5.2.3 under Mac OS X 10.4.11 (the last ever version of IE for the Mac) and it also failed to run the test and scored nothing.

    I would guess Safari 3 beta for Windows would be scoring the same as the Mac version, anyone tried it?

  34. Thanks for the response rob regarding Safari on Windows.

    It just goes to show that Apple deliver equally good software for all the platforms they develop for, while Microsoft insist on pushing deliberately inferior versions on anything other than Windows (e.g. MS Messenger, Office, RDC Client, etc. etc. etc. for Mac).

  35. The just released Safari 3.1 scores a solid 74/100 (and says ‘LINKTEST FAILED’). I believe Safari now has the highest score of the Big 3!

  40. Yeah, actually I do too. I’ll have to check the version I tested on at work. They have been adjusting the test over the past few days so maybe we’re seeing a byproduct of that.

  43. Хм… Пока это у нас не очень сильно развито, так что придётся подождать.

  46. kmeleon ccfme 0.09beta3 gets 87/100

    en español: kmeleon ccfme 0.09beta3 obtiene 87/100

    una pregunta cual es mas nuevo esta versión o la que dice 0.86 xul

  47. Pingback: I have no problem taking from the rich « ModestoBuzz
  48. Pingback: 随机记事 » Acid3测试发布
  50. Pingback: Best Of March 2008 « Smashing Magazine
  51. Pingback: Geek is a Lift-Style. »Archive » Best Of March 2008

  52. For Laughs I Tested IE5.5 Yes, Internet Explorer 5.5 I Went O.O, Yes Seriously It Runs The Test. Score Is 13/100

Leave a Reply

Your email address will not be published. Required fields are marked *