Recommended Posts

None have passed yet. Browsers must:

(1) pass all 100 tests

(2) pass those tests smoothly at 30fps or higher on each test

(3) present pixel-perfect rendering.

Safari and Opera WinGogi have met criteria (1) and (3). They both fail to meet criteria (2). Safari has performance problems with 2 or 3 of the tests while Opera WinGogi has problems with the same tests but also a few others. Right now, Safari is in the lead.

Most people are very interested in browser compatibility with standards these days, really strange!. I think is just another excuse to support the browser of their preference, more than the fact of the the advantages that brings the support or not support these standards :hmmm:

Standards are important. They make the job of a web developer infinitely easier. When a web developer has to hack around the inability of other rendering engines to do things properly, it creates messy code, extra work, and confusion.

interesting, FF 3.0 beta5 gives a decent score. Bad score for opera though was expecting much more.

thanks.

Opera 9.27 is pre-Krestrel, WinGogi is post-Kestrel. I doubt Opera will be adding any more Acid3 fix to their pre-Kestrel stable builds since it should be more about usability than passing a fancy artificial test. I'd like to see them fixing their 9.2x compatibility issues with the latest Flash instead of trying to merge stuffs from their highly unstable WinGogi experimental builds into their current stable builds to get a few more scores in Acid3.

Opera 9.5 beta gives better result than FF 3 beta 5. "Failed 22 tests" for Opera 9.5 build 9864.

I think the last Kestrel weekly scores 79/100.

Standards are important. They make the job of a web developer infinitely easier. When a web developer has to hack around the inability of other rendering engines to do things properly, it creates messy code, extra work, and confusion.

However, the Acid3 mainly doesn't test the browser to make sure it can support what features the standards include, but rather to make sure it does NOT support what features the standards exclude...

....

Safari has performance problems with 2 or 3 of the tests while Opera WinGogi has problems with the same tests but also a few others. Right now, Safari is in the lead.

I don't think so. I think the current WebKit nightly and the Opera WinGogi both have two problems in Acid3, but one of them differs.

WebKit:

snap3vh9.jpg

WinGogi:

snap4ce1.jpg

The difference is that WinGogi has a less than perfect pass of test 69 for taking more than one attempts at it, while WebKit takes more than 0.5s in test 65.

Also somehow WinGogi can consistently achieve a total time of around 1s, less than WebKit's total time of around 3s, when both are loading from cache.

  • 4 months later...

Serious?

Acid3 don't mean anythng in real world at present and near future, innovation, security, performance to name just 3 things are far more important.

These test should be for developers only, as at present its mis-guiding the ignorrent to how good browser is.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Anyway to download these versions without being on the Experimental builds?
    • Nothing is stopping you from continuing with your testing cadence. If updates are released every 2 weeks instead of 4, and you test once every 4 weeks, the exact same amount of patches will still be available for you in those 4 weeks. For example: Before 4th week - patch 1, 2, 3, 4 After 2nd week - patch 1 and 2 4th week - patch 3 and 4 Still the same amount after 4.
    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!