Home > Acid > Update on Opera's Acid2 progress

Update on Opera's Acid2 progress

August 1, 2005

It’s finally starting to smile, with the latest internal build of the Opera browser.

The Acid2 test got a face-lift from Opera — the smile is now complete.

“Most of the work is being done on a new branch of the core Opera code“, according to Opera’s Tim Altman, “the public won’t be seeing these updates for a while, though, as we still have plenty of work to do on this code branch before it goes public.”

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.

Apple’s Safari browser is “purportedly” the only [major] browser to have passed the Acid2 test (in their internal builds).

Update (4:39 PM): According to Opera’s CTO, Håkon Wium Lie, Opera is ‘very close’ to passing the Acid2 test.

Opera's Acid2 progress - Latest internal build
Latest internal build

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

Categories: Acid
  1. Anonymous
    August 1, 2005 at 11:50 am

    What’s an internal build?

  2. August 1, 2005 at 12:03 pm

    What’s an internal build?

    An internal build of Opera is a new working version of Opera that is only available internally to the Opera company — i.e. it has not been released yet to the public.

    Sorry, for not pointing that out.

  3. August 1, 2005 at 1:15 pm

    Nice to see some progress! I don’t expect much in IE 7 or Firefox 1.5 (I think all the Acid2 work is slated for FF 2.0), but between Opera and Safari, it’ll be great to start seeing these fixes work their way into releases that are actually in use.

    A point of correction: Since internal Safari builds passed Acid2 in April, Konqueror and iCab have also passed it. iCab actually beat Konqueror for second place by a matter of days.

    The Konqueror fixes are still only on the development tree (just like Safari, though they had to implement a lot of the fixes from scratch since the KHTML and WebCore codebases have diverged quite a bit), but the iCab fixes are in the latest public beta. AFAIK it’s still the only Acid2-compliant browser you can just download and run.

  4. August 1, 2005 at 1:19 pm


    Thanks for pointing that out. I forgot about those two browsers.

    Updated post.

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