Home > Acid, Desktop > Latest weekly build of the Opera browser passes Acid2 test

Latest weekly build of the Opera browser passes Acid2 test

March 10, 2006

The most recent weekly build of the Opera desktop browser, which was released today, has passed the Acid2 test (see screenshots below).

The Acid2 test has been written to help browser vendors make sure their products correctly support features that are part of web standards.

Acid2 tests for features that are part of existing standards but haven’t been supported by major browsers. Acid2 is a complex web page. Though not all web standards are tested, it uses features that are not in common use yet, because of lack of support, and it crams many tests into one page.

Konqueror and Apple’s Safari browser have also passed the Acid2 test.

It’s finally smiling.

Opera's Acid2 progress - Latest Weekly build (#8265)
Latest Weekly build (#8265)

Opera's Acid2 progress - Opera 9 TP2
Opera 9 TP2

Opera's Acid2 progress - Opera 8.02
Opera 8.02

Opera's Acid2 progress - Opera 8.0
Opera 8.0

Opera's Acid2 progress - Opera 7.54
Opera 7.54

Advertisements
Categories: Acid, Desktop
  1. Anonymous
    March 10, 2006 at 1:04 pm

    Don’t forget the public beta of iCab 3!

  2. March 10, 2006 at 1:45 pm

    I am not sure if it was a public build but I believe that Camino had also achieved this feat.
    Anyway well done Opera 🙂

    But this was expected.The real big news and also a big step forward will be if and when Ie passes this test.It’s just so annoying now, as Ie fails to render a lot of properly coded pages currently.

  3. March 10, 2006 at 2:18 pm

    No, Camino hasn’t passed it. Camino uses the Gecko rendering engine, same as Firefox, Mozilla, and Seamonkey. Even on the trunk (where all the active Gecko development is going on), Gecko isn’t even close to passing Acid2 yet.

    Congrats to Opera!

  4. kL
    March 10, 2006 at 4:11 pm

    Great! So that’s two left: Explorer and Gecko.
    Mozilla plans Acid2 fixes for refactored Gecko 1.9, which will be released in Firefox 3 somewhere around Q1 2007.

  5. March 10, 2006 at 8:31 pm

    Awesome. Let’s just hope they don’t have to roll back any of those fixes to iron out any remaining showstopper bugs. Acid2 is exciting, but I’d much rather 9.0 just work for people. eg. more DOM2 Style support, no more occasional GDI flakiness…

  6. Anonymous
    March 11, 2006 at 3:42 am

    Screenshots always must be in PNG, not JPEG. PNG size is smaller and no visual artifacts there.

  7. March 11, 2006 at 9:36 am

    Kelson, you claim that Gecko isn’t even close to passing the Acid2 test, look at the 1.6 builds, as buggy as they might be they have come a long way.

    I’m a Firefox user.

    Anyway congratulations to Opera for achieving this feat. It has come along way from Opera 7.54 and Opera 8

  8. arkavat
    March 11, 2006 at 1:58 pm

    😦

    I doubt if opera can claim to have passed the acid 2 test.. as of yet.
    just scroll the page and u’ll see that the rendering fails.
    but still its way better than gecko…

  9. Anonymous
    March 11, 2006 at 2:21 pm

    Aah.

    This a dev. version.
    Before complaining about Gecko take it the test with 1.6 (which is hardly stable). 1.6 is a pre pre alpha. And If IE7 passed it, it would be breaking 90 % of webpages.

    I’m sure Firefox will be able to do the same.

    And since Acid2 use stuff no webmaster cares about, is it really that important

  10. Anonymous
    March 12, 2006 at 4:45 am

    @ arkavat

    i read that the acid test page ISN’T SUPPOSED to be scrolled – if it is, it’ll always result in strange things on the screen. you shouldn’t scroll that page – when you do scroll and it breaks, it doesn’t mean the browser’s rendering is broken.

  11. March 12, 2006 at 8:31 pm

    Obviously this won’t “count” until it’s officially released; but it’s still awesome news 🙂

    I guess this would make Opera the first cross-platform browser to pass Acid2? Certainly good news for CSS prototyping.

  12. Anonymous
    March 13, 2006 at 7:51 am

    IE is not standards-compiliant = “IE sux, MS sux, [other browser here] rulez!”

    Opera is standards-compiliant = “it doesn’t matter, webmasters don’t care, and I know that buggy page that doesn’t work”

    Pathetic.

  13. March 13, 2006 at 1:35 pm

    Who’s “complaining” about Gecko? 1.9 is a lot further than 1.8, but it’s not done yet.

    Or is it impolite to check in on other browsers’ progress?

    On the issue of whether Acid2 is important because it checks things that “no webmaster cares about” — that’s a chicken-and-egg problem. Acid2 is about filling in the corners. Once those corners are filled, webmasters will have more tools to use. It’s not a compliance test by any stretch of the imagination — there are still plenty of areas in the middle with spotty cross-browser support (even ignoring IE). But anything that raises the bar on what capabilities the major browsers have in common is going to improve matters.

  14. Anonymous
    March 13, 2006 at 1:56 pm

    Yeah. Until mr. Dotzler comes along and posts another one of those famous posts of his, like “Opera falls into line again” or “Acid2 is useless, Opera should’ve spent time doing this or that” and “We are the leaders”.

  15. Anonymous
    March 13, 2006 at 10:57 pm

    Asa’s actually a woman.

  16. Anonymous
    March 15, 2006 at 9:34 am

    Only Safari and Opera pass Acid2. iCab and Konqueror show scrollbars, right? Then they fail.

    And scrolling is not part of Acid2, so that it breaks when you do is expected.

  17. March 16, 2006 at 8:56 am

    Prince passes Acid2 as well.

  18. Rade
    April 12, 2006 at 3:42 pm

    Firefox (on a development branch) passing the Acid2 test! Screenshot

  1. No trackbacks yet.
Comments are closed.
%d bloggers like this: