Slashdot Mirror
Acid3 Test Released
An anonymous reader writes ""The Web Standards Project has announced the release of Acid3, the latest test designed to expose flaws in the implementation of mature Web standards in 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.' Screenshots at the Drunken Fist site show the success of Safari 3 (which originally scored 31, but is now Scoring 87/100) IE6, and IE7 (massive fail, of course)'." There are additional discussions of the new test happening around the web.
the test is here.
i'm getting a 50/100 in Firefox.
Why does slashdot keep linking to dead blogs?
The actual test is http://acid3.acidtests.org/ here.
My UID is prime and so is this number: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0.
3b3 gets a 61. Opera 9.5 is the best I tested at 65. Safarai 3.0.4 for Windows got a 39. IE7 got a 12 and also managed to mangle the page the most.
90/100.
Getting pretty close.
The Mothership
I just tried it on Opera 9.5 Beta, build 9755. I got a 60/100. Then I tried again and got a 61/100. Then a 60/100 on a third try.
All of the rectangles are grey (two different shades), the test name is red and does not have a shadow, and there is an x in the upper right hand corner.
I haven't seen anybody answer konqueror yet!
I tried it in Konqi 3.5.8 with Gentoo. It asked me what I wanted to do with "empty.txt" then segfaulted. Anyone fairing better?
See http://browsershots.org/http://acid3.acidtests.org/ for the test in 75 different browsers.
Wikipedia: http://en.wikipedia.org/wiki/Acid3 also lists the results for the developversions of browsers:
Webkit: 87
Firefox: 67
The test consists largely of 100 JavaScript tests designed to throw an assertion on failure and return a certain value on pass. The score is how many of the tests out of 100 pass. You can see which tests failed by clicking or shift-clicking the A in Acid3 after the test completes. In the sense that each test can relatively independently pass or fail (although some tests depend on previous tests), yes, it is a quantitative test.
The other part of the test is rendering the Acid3 text with shadow and the colored rectangles. By seeing how the Acid3 test fails in many other browsers, you can see that it can also render X, Fail, and a picture of a cat on failure of some rendering tests, typically in red so they stand out.
What a fool believes, he sees, no wise man has the power to reason away.
If they actually implemented the standards well, they wouldn't have to worry about specific tests, they would just do well on them by default.
Have you ever tried reading the HTML/CSS specs? They're huge and often vaguely worded. There were often sections that just weren't intuitive, and the only real approach to implementing them was to just figure out what other browser did and copy it. The specs were created by people who have no intention of implementing them themselves, and it really shows.
It's misleading for the summary to say "Safari" gets 87/100 when the version of Safari that does that is not yet released.
Run current WebKit nightlies to get the high score now. The changes will be in the upcoming Safari 3.1 release.
Why Isn't IE8 Passing ACID2?
Basically, it fails because of XSS on the other sites.
If these acid tests are based on standards. Why is the only acid test that passes the W3C validator, the Acid 1 test?
Because more recent Web standards include sections on how certain kinds of errors are supposed to be handled. These need to be tested just like everything else, but up until Acid2 many browsers weren't very good about that.
Remember, the point of Acid tests is to be a thorn in browser developers' sides: find areas of the standard that no one currently does well and test for them. Browsers shouldn't pass Acid tests when the tests first come out: that would be missing the point of the tests in the first place.