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.

15 of 309 comments (clear)

  1. Bad day for IE8 by Anonymous Coward · · Score: 5, Funny

    It gets... 17. Heard at Microsoft "ACID3? We just passed ACID2! AH CRAP!"

    1. Re:Bad day for IE8 by jimbojw · · Score: 5, Funny

      Hey now, at least it passes the reference rendering, which is more than I can say for some browsers (*cough* lynx *cough*)

  2. Re:Firefox by brunascle · · Score: 5, Informative

    the test is here.

    i'm getting a 50/100 in Firefox.

  3. Re:Of Course IE will fail, ACID test is biased... by setagllib · · Score: 5, Insightful

    Yes, biased towards conforming with open international published standards, rather than to any specific vendor's implementation. It just happens the best of the best web browsers try to conform to the same standards, scoring much higher than Microsoft's offering which is deliberately designed to break from the standard to ensure lockin.

    --
    Sam ty sig.
  4. Latest Safari nightly scores... by The+Ancients · · Score: 5, Informative

    90/100.

    Getting pretty close.

  5. Re:Firefox 2.0.0.12 by thornomad · · Score: 5, Funny

    Woo hoo! IE 6.0 displays this just fine: http://acid3.acidtests.org/reference.html Read 'em and weep Firefox!

  6. Re:Of Course IE will fail, ACID test is biased... by moderatorrater · · Score: 5, Insightful

    Not quite. When none of the browsers are getting 100/100 and the only browser to get over a 60 is a safari beta, I think it's safe to say that it's a test designed so that every browser will fail. That's the point: they're giving solid targets to browser developers and giving a concise score to everyone else so that they know where the browsers stand in the next generation of web tech.

    So, I guess what I'm saying is that complaining about it being designed so that IE would fail is like saying that American Gladiators was designed so that my 8 year old brother would fail. Sure, it has that effect in the end, but the fact that he's under-equipped for such a competition isn't American Gladiators' fault.

  7. Konqueror by kevmatic · · Score: 5, Informative

    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?

    1. Re:Konqueror by Anonymous Coward · · Score: 5, Informative

      That crash is fixed in 3.5.9 (which does 41)... 4.0.2 does 61, 4.1-pre 63. Early 4.0.x versions do less.

  8. Slashdoted by fluch · · Score: 5, Funny

    Conclusion: ACID3 test didn't pass Slashdot test. Too bad.

  9. Re:Firefox by bunratty · · 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.

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  10. Re:Firefox by Random+BedHead+Ed · · Score: 5, Funny

    Hey, me too. Are you also using Netscape Navigator 4.01?

  11. Re:Perhaps.... by bunratty · · Score: 5, Insightful

    Yes, there is almost no correlation between how well a browser does on Acid tests and how well it renders pages on the web. The purpose of the Acid tests is to break the chicken-and-egg problem of web development. The web developers tend not to use features unless all popular browsers support them. On the other hand, the developers of the web browsers tend not to add features that are not used by web developers. Without anyone willing to go first, the implementation and use of new web standards stalls.

    The purpose of the Acid tests is to break this logjam by using these new standards in a very public way so that web developers will be motivated to implement them. The "my browser does better than your browser" posturing is a bit immature, but as a side effect it popularizes the faults of browsers and motivates the browser developers to fix them. Then, the web developers use the new features after they are well supported.

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  12. Re:I would check out the screen captures, but... by emilper · · Score: 5, Funny

    yes, looks like the acid tests are failing the slashdot test.

  13. Re:Firefox by dal20402 · · 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.