Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firefox Beta Scores 93 On Acid3 Test

Posted by CmdrTaco on from the scored-worse-on-meth2-test dept.

CodeShark writes "Mozilla released their latest Firefox 3.X beta today (3.5b4), and increased their score on the Acid 3 test to 93 [on my XP laptop], with tests 70, 71, and tests 75-79 being the final challenges. Curiously though, the current release of the top Acid3 performer — Safari — still not only rates higher (I got scores of 99 once and 100 most of the time) but is usually faster by a little (1.1 sec avg. vs. 1.4 over ten runs apiece) but only because the new Firefox beta was all over the map — frequently better by 25% (.85sec) or tanking badly with rendering times in the 2.5 — 3 second range, and both suffer performance hits on one test (#69)."

6 of 282 comments (clear)

  1. Opera 10 as well by Anonymous Coward · · Score: 5, Informative

    Opera 10alpha is also a 100/100 on the acid 3 since dec 12, 2008

    http://www.opera.com/docs/history/

  2. Acid2 already looks fine in Fx 3.0.10 by tepples · · Score: 4, Informative

    How does it rate on Acid 1 & 2, and have the other browsers worked on reaching 100% on the previous tests also, or did they give up on previous tests when the next one was released?

    Acid2 already looks fine in the latest general release version of Mozilla Firefox.

  3. 96/100 with svg.smil.enabled set to true by bunratty · · Score: 4, Informative

    Firefox 3.6 builds score 96/100 when you set the preference svg.smil.enabled to true because tests 75 and 76 require SMIL in SVG. You can find the four tests that Firefox 3.6 still doesn't pass on the Acid3 spreadsheet.

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  4. Garbage collection by tepples · · Score: 5, Informative

    Presumably the test should take about the same time to run each time, right?

    One of the 100 tests is JavaScript garbage collection. A garbage collector that uses tracing without reference counting isn't necessarily guaranteed to finish in a given amount of time.

  5. Re:Why the variation? by auzy · · Score: 5, Informative

    One of the tests is related to rendering speed (#69) not design faults. That's because it wants the test to be completed fast enough to achieve 30fps.

    Under system load, or browser load (such as extra stuff being done in the rendering thread whilst the test is running), a browser may not always pass this test. Whilst its an OK test, there will be no way to reliably pass it 100% of the time, and as CPU's become faster and more efficient, its likely browsers will pass eventually regardless of if they optimise their code or not.

    Its also one example of why the ACID tests are quite overrated.

  6. Re:Safari and Chrome bound to get better? by vitaflo · · Score: 4, Informative

    Were adblock and flashblock available for Safari or Chrome (and I believe this is in development for Chrome), and were Chrome available as a Mac version, I would stop using Firefox overnight.

    Adblock has been available for Safari for years now. You can get it here:

    http://safariadblock.sourceforge.net/

    A Flash block addon for Safari is also available:

    http://hetima.com/safari/stand-e.html

    While Safari doesn't have the same ease of plug-in support as Firefox, there's enough for most people who want to make the switch.