Slashdot Mirror

← Back to Stories (view on slashdot.org)

First Look At the ACID3 Browser Test

Posted by kdawson on from the turn-on-tune-in-render dept.

ddanier writes "Now that all major browsers have mastered the ACID2 test (at least in some preview versions), work on ACID3 has begun. The new test will focus on ECMAScript, DOM Level 3, Media Queries, and data: URLs. 100 tests will be put into functions each returning either true or false depending on the result of the test. The current preview of ACID3 is still missing 16 tests."

3 of 133 comments (clear)

  1. Various Scores by The+MAZZTer · · Score: 5, Informative

    Final scores of course are subject to change on the final test:

    • Firefox 3 beta 2 @ Windows XP: 62%*
    • Internet Explorer 7 @ Windows XP: Dear God... you need to try it yourself. Viewing the generated source is needed to see the result is 24%
    • Opera 9.5 build 9721 @ Windows XP: 65%
    • lynx and elinks @ Windows XP: No JavaScript support. :(
    • Opera 9.3 @ Wii: 61%
    • Opera 8.5 @ Nintendo DS: 1%

    * - script takes long enough to run that browser prompts you to kill it.

  2. Re:I bet some devs are really pissed now by Anonymous Coward · · Score: 5, Informative

    No, it isn't.

    Which is why the GP shouldn't be modded as "Insightful."

    The ACID Tests are meant to test certain parts of the proposed standards.

    Passing the Test doesn't imply standards compliance.
    BUT
    Standards compliances DOES imply passing the tests.

  3. Re:Where is the reference image from? by gsnedders · · Score: 5, Informative

    Yeah, it was David Hyatt who was working on getting Saf to pass (and got it to be the first browser to pass in any build, and the first to have a generally available release (i.e., a non-development build, even if public) -- the latter being the only thing that truly counts for passing the test).

    http://weblogs.mozillazine.org/hyatt/archives/2005_04.html#008011 details the bug (in this case, it was the test itself that was wrong -- not the reference). The reference rendering for Acid3 is likely correct as the actual rendering isn't overly complex (the complexity is in the ECMAScript and DOM support), though with the complexity of some tests there could easily be bugs in the test again.