Acid3 Test Released 309
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.
Firefox 2.0.0.12 (Score:3, Informative)
Re:Firefox (Score:5, Informative)
i'm getting a 50/100 in Firefox.
Link to the actual test (Score:4, Informative)
The actual test is http://acid3.acidtests.org/ [acidtests.org] here.
Re:Firefox 2.0.0.12 (Score:5, Informative)
Re:Bad day for IE8 (Score:3, Informative)
Latest Safari nightly scores... (Score:5, Informative)
90/100 [mothership.co.nz].
Getting pretty close.
Re:Opera (Score:5, Informative)
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.
Re:Firefox (Score:0, Informative)
Re:Firefox (Score:3, Informative)
Anyway, Opera 9.50.9807 receives a 65.
Re:Firefox (Score:2, Informative)
Konqueror (Score:5, Informative)
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?
Re:Konqueror (Score:5, Informative)
Re:Firefox 3 beta 3 (Score:3, Informative)
Results in major browsers (Score:4, Informative)
Wikipedia: http://en.wikipedia.org/wiki/Acid3 [wikipedia.org] also lists the results for the developversions of browsers:
Webkit: 87
Firefox: 67
Re:Firefox (Score:5, Informative)
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.
Re:Of Course IE will fail, ACID test is biased... (Score:2, Informative)
Not to mention... (Score:3, Informative)
Faster than FF3 beta 4, much much faster than FF2 or IE7.
Re:IE8 Cheats ACID2!! (Score:0, Informative)
Re:IE8 Cheats ACID2!! (Score:2, Informative)
Re:Firefox 3 beta 3 (Score:4, Informative)
Put another way it looked really hard for things to test that would give browsers low scores.
There's nothing to say that the things it tests are necessarily useful. Some are, some are not.
Re:Perhaps.... (Score:3, Informative)
The test is about making life better for web developers, and about making the web more interoperable, instead of having sites which jump through browser predicated hoops, or restrict users to "IE7.0 or newer on 32-bit Windows" or the like. Thus having your favorite browser, and your least favorite browser score well is in the best interests of all web users.
Re:Too late for IE8? (Score:5, Informative)
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.
Re:Geek version of a measuring contest? (Score:1, Informative)
Re:IE8 Cheats ACID2!! (Score:2, Informative)
IE8 fails when it runs in quirks mode, and passes when in standards mode. Before it would run in quirks by default, and only change behavior when it visited certain key sites, or sites had a tag.
That url would be one of those "key sites"
However if the previous slashdot story is true, IE8 should eventually operate in standards mode by default, so it will pass both.
Re:Firefox (Score:5, Informative)
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.
Re:IE8 Cheats ACID2!! (Score:2, Informative)
Re:Of Course IE will fail, ACID test is biased... (Score:3, Informative)
So IE or Opera failing was actually regarded as insufficient.
Re:Firefox (Score:3, Informative)
Re:IE8 Cheats ACID2!! (Score:5, Informative)
Basically, it fails because of XSS on the other sites.
Re:W3C validator (Score:5, Informative)
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.
Re:Bad day for IE8 (Score:3, Informative)
What OS? Opera 9.5 beta works fine for me on OS X and gets 59/100. The only things that crashed for me were Shiira on OS X and Konquerer 3.5.2 on Kubuntu.
Note, the best score I'm getting is from Safari 3.0.4 with a nightly Webkit on OS X, with a score of 86/100.
Re:Firefox 2.0.0.12 (Score:1, Informative)
Acid 3 is mostly Hixie, who's currently at... Google, I think. Previously Opera/Netscape.
Aside: yes, he did ask for browser developer feedback (in particular, to look for things that will fail in under-development versions of Mozilla and Safari; presumably, Opera too.) Apparently new things that only failed in IE wasn't interesting. Reference: his blog [hixie.ch].