Slashdot Mirror

← Back to Stories (view on slashdot.org)

Acid3 Test Released

Posted by Zonk on from the new-is-better-than-old dept.

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.

4 of 309 comments (clear)

  1. Re:Firefox by caerwyn · · Score: 4, Interesting

    Interestingly, I'm not getting an 87 with Safari 3.0.4- I'm getting a 39.

    --
    The ringing of the division bell has begun... -PF
  2. Re:Firefox 2.0.0.12 by Jugalator · · Score: 3, Interesting

    Opera 9.5 is the best I tested at 65. It better be good, since Håkon Wium Lie, Chief Technical Officer of Opera Software, worked together with Bert Bos to develop the CSS standard.

    I'm not sure how many actually knows this. *shrug*
    --
    Beware: In C++, your friends can see your privates!
  3. How do the acid-test creators test the acid test? by dskoll · · Score: 4, Interesting

    Seriously... if no browser gets 100/100, how do the test creators generate the reference image? And how do they know there are no bugs in their test? I'm genuinely curious...

  4. W3C validator by atomic-penguin · · Score: 3, Interesting
    If these acid tests are based on standards. Why is the only acid test that passes the W3C validator, the Acid 1 test?

    1. Acid 1
    2. Acid 2
    3. Acid 3


    Perhaps, I am missing the point of these acid tests. I'm not a web developer by trade, so I don't claim to be an expert on CSS. From personal experience, CSS has allowed me to use much less complex HTML in the little web publishing I have done. I never seem to get consistent results when I test my pages in different browsers. I hope that these "standards" Acid tests lead to greater compatibility across browsers.

    Do these tests increase compatibility by pushing the envelope on new standards, or are they just a browser-war pissing contest?
    --
    /^([Ss]ame [Bb]at (time, |channel.)){2}$/