Topic: Acid3 : checked.

Holy Moly! The latest WinGogi build of Opera* scores 100/100 in Acid 3.

I'm looking forward to check this out for myself tomorrow morning, and see a public build.


*: WinGogi the Windows version of Opera's reference builds used for the internal testing of Opera's platform independent Core.

Uhh...Poi?

Not meaning to slam the brakes on ya, but this

quote:

---

Opera employee David Storey writes on his blog that they've overtaken Apple's browser in the Acid3 test. In the race to be the first to reach the reference rendering, Opera's software leads now with 98%, closely following by Safari with 96% and Firefox 3 beta 4 with 71%. He also noted the implemented features will not make a public appearance in the following weeks, because they are getting close to releasing Opera 9.5. That version has been under public testing since September and the new CSS3 color modes and font rendering features might further delay this. They will probably show the score in a preview build soon and wait for a post 9.5 stable build to release the new features to the public."

---

So...whuppty-doo-dah.

So they said they reached 100%.

But it is not going to get released.

Yet.



WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

Nothing new under the sun. Like FireFox 3, Opera 9.5 is too close to final release to merge the fixes/additions made to approach or pass Acid3.

It is very common that browser vendors announce internal progress, including passing, on such tests. See how many passed Acid 2 internally and then released a public build weeks later. Public builds have to be stable : make sure no regression occured, broaden the support of specific parts of a standard tested in an Acid test, ...

FYI the Gogi builds include in progress features : for Opera 10, for different platforms, for specific customers. Therefore Gogi builds can not be released publicly. That's why a few days/weeks are needed before we can release a public desktop build showing the 100/100 score in Acid3.

So yes Opera 9.5 will most likely not pass Acid 3, but 9.6 or 9.7 might very well pass it.



(Edited by poi on 03-27-2008 02:10)

Something that may be of note to some people: the criteria for passing the acid3 test is not only to score 100% (!): the animation must also be smooth (something that cannot be discerned from a screenshot), and the text underneath must be correct. In the screenshot I saw, there was a space missing after one of the commas. This is not to criticize at all - this is a tremendous effort

Wrayal

Yeah! the webKit guys got pumped up and apparently the latest webkit nightly passes Acid3, although they admit not being really smooth on the animation. And of course as one claimed to pass, the test has been corrected a bit. So Opera might be down to 99. We'll see. Anyway it's good to see browser vendors being that commited to the standards.

I guess we'll soon see a Safari 3.2 or 3.3 passing Acid 3



(Edited by poi on 03-27-2008 10:32)

Yes, but the WebKit can be DLed and used, right?

WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

Yes of course since webKit is an open source application framework.

So will FF3 hit Acid3 at 100%? Any idea when FF3 will be out?

Sooo...currently, only Webkit (because it is available and can actually be tested by customers) clears the Acid3 test.

Right?

WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

quote:

---

WebShaman said:
Sooo...currently, only Webkit (because it is available and can actually be tested by customers) clears the Acid3 test.

Right?

---

No browser passes all conditions yet, but according to the WebKit weblog they only have the animation smoothness left. Opera is back at 99 % as poi said (although probably at 100 % again internally).

Personally, I don't really care who's first, I just think it's impressive work by both vendors. Congrats to poi and Opera, and congrats to the WebKit team (as they are both there soon).

WebShaman: If you will. Then IE passed Acid2 on March 5, 2008 not on December 19, 2007, and Safari passed Acid2 on October 31, 2005 not on April 27, 2005, ...

Moot point, but in your last post s/customers/end users

HZR: Thanks. I have nothing to do with the passing of Acid3

Yep, the more browsers passing or approaching such tests the better. I'm also quite happy with the noise about perfomance and memory tests lately.

I open this thread because it is/was a news. I'd had open this thread even if webKit or anybody else had passed Acid3 : public build or not.

Actually it was a news even for me, before leaving the office yesterday I was stunned to hear we had a build scoring 98 while our current public builds are flirting with the 80 mark. And a couple of hours later bam! 100. Afaik we're back to 100.

quote:

---

HZR: Thanks. I have nothing to do with the passing of Acid3

---

I know, I know. But you work for the company, so you deserve the congrats

quote:

---

WebShaman: If you will. Then IE passed Acid2 on March 5, 2008 not on December 19, 2007, and Safari passed Acid2 on October 31, 2005 not on April 27, 2005, ...

Moot point, but in your last post s/customers/end users

---

Exactly.

Though I do find it more than encouraging to see most of the major Browser Teams taking the Acid tests seriously.

Unfortunately, the major one that is missing, is the one with the biggest market share

WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

as always!

Blaise: FF3 won't pass Acid3, it's too close final release to introduce unnecessary risks of regressions.

The beta 4 was released recently, not long after beta 3, and it seem they plan a short lived beta 5 before going final. So I take it FF3 will be released in mid-late April.

Hmm, interestingly, the latest webkit build gets 100% for me...sometimes. About 50% of the time, it only gets 99%, with:

test 80 failed: kungFuDeathGrip was null

Also, tests 26&79 took too long - do others' experiences correspond to this?

I think FF should concentrate as they have been on first cleaning up the product (re : memory leaks) before they bend their efforts to passing the Acid tests.

WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

(Edited by WebShaman on 03-28-2008 15:51)

FWIW I just saw a Gogi build score 100/100 on the current Acid3 test, with the whitespace between the ',' and the 'a'. Tests 26 & 79 seemed to be a little slow, but from what I've heard these tests are rather hacky anyway with the time allowed for the animation decreasing with the system date. Dunno the details of this slightly magic/arbitrary calculation.

Here comes the winGogi and linGogi builds showing Opera's core score100/100 with pixel perfect result. It scores 100/100 all the times. No need to refresh and cross your fingers.

As expected the report ( click the A ) on my machine says:

quote:

---

Failed 0 Tests.
Test 26 passed, but took 328ms (less than 30fps)
Test 69 passed, but took 3 attempts (less than perfect).
Total elapsed time: 2.72s

---

And when do you expect an Opera version out that actually does this?

WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

As I said earlier 9.5 is too close to final release to introduce new things but I wouldn't be surprised if 9.6 or 9.7 were the first official releases of Opera to pass Acid3. I don't know the timeline though if this is what you are looking for. Sorry.

So my money is still on a Safari 3.2 or 3.3 for the first official release.



(Edited by poi on 03-28-2008 16:13)

So it might be 9.6 or 9.7.

Ok, thanks.

WebShaman | The keenest sorrow (and greatest truth) is to recognize ourselves as the sole cause of all our adversities.
- Sophocles

"Test 69 passed, but took 3 attempts (less than perfect)." - seems slightly arbitrary that this is considered better than the test for which Webkit which on average takes 2 attempts :P I know this is a programmatic thing and test 69 has repeat attempts included, but still...all kidding aside though, great work by the Opera team Great to see such progress!

quote:

---

poi said:
*: WinGogi the Windows version....

---

and who is the guy in charge coming up with the funny build names?

You should see the list of internal names for Opera's different modules... They are often quite witty.

As for GOGI, the expansion of the name is "Generic Opera Graphics Interface".

--
var Liorean = {
abode: "http://liorean.web-graphics.com/",
profile: "http://codingforums.com/member.php?u=5798"};