Slashdot Mirror

← Back to Stories (view on slashdot.org)

Opera 10 Alpha 1 Released, Aces Acid 3 Test

Posted by timothy on from the now-it-sees-all-the-spiders-and-tastes-color dept.

Khuffie writes "It seems that the upcoming version of Opera 10, of which the first Alpha has recently been released, has already passed the Acid 3 test with a 100/100. The only other rendering engine to have a complete score is WebKit, which can be seen in Google Chrome's nightly build. Opera 10 Alpha 1 will also finally include auto-updates, inline spell checking, and see some improvements to its built-in mail client, including much-requested rich text composition."

1 of 258 comments (clear)

  1. Acid3 != Standards Compliance by TodLiebeck · · Score: 5, Interesting

    Just tried it out, and of course it passes ACID3 as advertised. I still can't recommend this browser on the grounds that it can't correctly render absolutely positioned CSS elements, as demonstrated by the following code:


    <!DOCTYPE html
              PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
              "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
      <head>
        <title>Resize your browser with the vertical handle!</title>
      </head>
      <body>
      <div style="position:absolute;left:20px;right:20px;top:20px;bottom:20px;background-color:lime;">
      <div style="position:absolute;left:20px;right:20px;top:20px;bottom:20px;background-color:red;">
      </div>
      </div>
      </body>
    </html>

    Hosted version of the above:
    http://echo.nextapp.com/content/test/operacss/

    Opera 9.50, 9.60, and now 10.0alpha will not render the above properly if the browser is resized vertically. (9.27 and prior work perfectly) On the initial render, 9.5/9.6 and 10 do fine, but the moment one resizes the browser vertically (and NOT horizontally as well), things go awry. I reported this to their bug tracker six months ago, and posted a thread on their forums 2.5 months ago: http://my.opera.com/community/forums/topic.dml?id=250572 Have also mentioned it in their 9.6-about-to-be-released-post-non-working-sites thread.

    This bug has additional consequences for AJAX applications that make use of on-screen measuring using offsetWidth/offsetHeight information. In such cases, even the initial rendering can be seriously flawed as offsetHeight returns incorrect values. (Note: offsetXXX properties are not part of a proper W3c standard, but are universally supported).

    Apologize for the quasi-rant, but I just don't want to see another bug report about how our applications don't look right in a supposedly ACID3 compliant browser, thus indicating that the problem "MUST" be our fault. Please realize that passing ACID3, while a neat accomplishment and generally good thing, is far from a guarantee of standards compliance.