Opera first browser to reach 100% in Acid3 test
Published March 26th, 2008 4:30 PM EDT By Daniel GoldmanCongrats to the Opera team on becoming the first browser to reach the 100% pass rate in the Acid3 test.
In an internal build of the Opera browser, the Acid3 test, which was only very recently released, reached a 100% pass rate.
A technical preview of this internal Opera build will be posted on labs.opera.com in the next week or so.
For now, the screenshot below shows Opera and the Acid3 test on the latest WinGogi Desktop build. WinGogi is the Windows version of Opera’s reference builds used for the internal Core testing.
It’s always nice to be first. 
Opera passes the Acid3 test!
using
Congratulations!!
Was hoping the Opera team would beat the Webkit and Mozilla devs, but it seemed Opera was slipping behind.
using
Daniel, I think you are wrong. As was said Opera has 100% of points in Acid3 http://www.css3.info/opera-overtakes-safari-in-acid3-race/ but this doesn’t by itself mean, that Opera passed whole Acid3. But Opera have to be really very close now.
using
Martin is right. Opera does not pass Acid 3. It passes the 100 DOM tests, but has a number of rendering issues. There are probably issues with the smoothness of the animation too. It is on track to pass the test however. It will probably be tight between Opera and Apple on who passes first. It is a shame most of our programmers are probably going to bed now though
The important thing really isn’t who passes first though. It is that we get support for the features that are being tested. I’ve got a big interest in CSS3, and by doing the work we are doing, we have HSLA and RGBA support, which is something I really want. We also have web fonts support, which will do wonders for typography on the web, once browsers are released with support, and there are a library of free high quality fonts available.
using
I’ve been watching the race between WebKit and Opera, obviously rooting for Opera, so this was welcome news when I checked the Desktop Team blog tonight.
Firefox is at 71 in a dev release according to Wikipedia… hopefully all three of the MOS browsers will soon have stable releases that pass!
Now if only the IE Team can catch up…
using
Thanks Martin and David for pointint that out. I’ve corrected the post.
using
http://webkit.org/blog/173/webkit-achieves-acid3-100100-in-public-build/
http://ln.hixie.ch/?start=1206578003&count=1
“Just as Reddit is celebrating Opera reaching 100/100, with the misleading headline Opera the first browser to pass the Acid3 test (hey, submitter: it wouldn’t hurt to read the Opera blog post before submitting it to Reddit), the Apple guys track me down and point out that there’s yet another bug in the test. With heycam’s help, we have now fixed the test. Again. This presumably means Opera is now at 99/100… the race continues!”
Opera didn’t reach 100% first, didn’t release any binaries first. Webkit still beats Opera to 100% and publicly releasing the build.
using
Opera posts a screenshot of 100/100 and Webkit releases a nightly build of 99/100 on the same day. I love Opera, but being able to run the test myself means so much more than seeing a screenshot. I won’t be surprised if Webkit nightlies hit 100/100 before the Opera build is released — though the test really isn’t passed until all requirements are met.
using
http://webkit.org/blog/173/webkit-achieves-acid3-100100-in-public-build/
Webkit has already hit 100/100 and the public release of the binary is available for download, unlike Opera trying to steal Webkit’s thunder but not having anything to show until next week and not even really reaching 100% with Ian Hixie’s blog(Acid3 creator) mentioning the bug.
using
press release that backfired :/
using
Nystor: It was not a press release and it did not backfire
using
Free: Opera did reach 100/100 first, but the test itself was changed after that. How convenient for Apple
(By the way, does the latest WebKit build pass Acid2?)
using
I thought Apple fanboys only hung out on Digg. It’s nice to see they’ve come out of the woodwork to argue this 100% Acid3 test claim.
using
@coxy: So funny, but I don’t use Apple OSX(you can see my browser and OS) and I don’t use Opera or Safari. I’m stating the facts, Webkit has passed Acid3 100/100 with PUBLICLY released builds that anyone can obtain to verify the results. I would even say Apple will release a new version of Safari and claim Acid3 pass on a released, non-beta/nightly version soon while Kestrel final release won’t even come close to the alpha WinGogi’s score.
Opera doesn’t pass as per Ian Hixie, the Acid3 author unless you like to argue that he’s wrong and has no PUBLICLY available builds so 3rd parties can verify the results and it won’t be available until next week. Even then one can see you can’t use the WinGoGi as a browser at all, it doesn’t even look anything like Opera 9.5, it’s just a toy to play with Acid3.
@x3: Safari has passed Acid2 since October 2005, a good 8 months earlier than Opera did, as per wiki unless you think wiki is wrong then you can correct it.
http://en.wikipedia.org/wiki/Acid2
using
Apple cheated to “pass”:
http://blog.codedread.com/archives/2008/03/26/webkit-nightly-not-smiling/
http://blog.mozilla.com/rob-sayre/2008/03/26/acid3-is-basically-worthless/ (see the “shameful” link)
@Free, did you test Acid2 in the latest WebKit build or are you just assuming that it didn’t regress?
using
Free:
(I) Opera never claimed to pass. But it did reach 100/100 before the test was changed.
(II) WinGogi is not a toy: “WinGogi is the Windows version of our reference builds used for the internal testing of Opera’s platform independent Core.” Why make misleading statements like that?
(III) I know that Safari has passed Acid2 in the past. The question was whether it still does in the latest builds.
using
I am using the latest WebKit nightly build (r31370). It gets 100/100 on Acid3, but test 26 makes the animation hiccup because it takes too long. This fact was also clearly stated in the Surfin’ Safari blog. Additionally, it also passes Acid2 perfectly.
@x3: The Acid3 test was changed because WebKit developers noticed that the Acid3 test made it necessary to break the SVG 1.1 spec. I don’t see that convenient for anyone, except anyone trying to use the Acid tests as verification that browsers adhere to broadly accepted specifications. Additionally, it begs the question of why Opera devs did not notice the same bug when they implemented their version…
using
@Geoff I’m guessing that Webkit devs are more on the bleeding edge than opera, for example text-shadow was there ages before Opera implemented it. Besides does latest webkit pass the css3 selectors test?
using
It passes 576 out of 578 tests, meaning that 41 out of 43 selectors passed. However, the remaining two selectors are reported as unsupported, not buggy.
using
Reguardless of the fact that the build isn’t public, and that the test doesn’t pass perfectly (a 100/100 score is great, but as David Storey points out, that’s just the DOM tests, and not the entire Acid 3 test), it’s still a great milestone for Opera. Even if Safari has builds out that completely and perfectly pass the test before Opera does, it’s still great to know that the developers are almost there. That, and the fact that the devs stayed up much of the night in order to get that internal build working, shows that Opera is commited to proper standards support. Even if it was handled as a competition with Apple, it still shows that Opera developers are willing to do whatever it takes to pass the test.
using
To put things into perspective, Opera current version passes under 50/100… Congrats Opera Team!
using
@Geoff
Why didn’t Opera notice it? Well, why didn’t the Acid3 authors notice it? According to Apple, Opera reported several other problems to the Acid3 authors, so what are you suggesting? A great conspiracy by Opera? How is the failed test even relevant here? I don’t get it. Angry that Opera reached 100/100 before Apple?
Or angry that Apple had to add hacks for specific fonts and such to pass?
http://trac.webkit.org/projects/webkit/changeset/31322
Hey, I can get any browser to pass Acid3, Apple style! Just paste this into your browser:
http://acid3.acidtests.org/reference.html
using
@theharmonyguy
Gecko 1.9 will not pass the Acid3 test. The test itself came way too late in the development process.
Mike Shaver explains here: http://shaver.off.net/diary/2008/03/27/the-missed-opportunity-of-acid-3/
using
They seem to have done that with everyone… Except Microsoft…
Microsoft has a rare opportunity here. It will be humorus to see how badly they fail in the end.
using
Ie8 starts in another competition, it is called ‘rendering the real world wide web’. It is much more important than publicity stunt. Anyone knowledeable enough to understand code behind acid3 knows that it is a test completly irrelevant to todays web.
passing acid3 does not make any browser better when it comes to dealing with real pages - like google, ms, yahoo or localised versions of youtube (that break badly in opera). And dont start about ’standards’. Real world has pages that are not standard. Web browser must render them well or it is useless.
IE8 indeed has a rare oportunity, and really big problem infron of itself - current beta is a great achievement for MS, but it still renders half of the web rather funny.
using
Congrats to Opera. I hope they release the new build soon.
using
Nystor = w2
w2 conveniently forgets that IE doesn’t have to support “the real world wide web”. After all, “the real world wide web” is forced to bend over backwards to support IE.
But hey, who cares about facts, eh, w2?
using
That’s very cool news!
Can wait for the next weekly…
using
Nystor, please watch this video. I know it’s about forums, but it applies to blogs as well.
using
For those who want to try a public build of the Opera preview that passes Acid3…
I tried it, and it works. Two of the tests run too slow to be a perfect pass, but it does get 100/100 and it is pixel-perfect.
using
@Oddity
Actually, I was angered x3’s comment that the change in the test was “convenient” for Apple; the reality is that the test was broken because the test expected non-standards compliant behavior. I was suggesting that if Opera got their browser to work under the old test, they were not standards-compliant. Further, if they were coding for standards compliance, not Acid3 compliance, they would have been the ones to submit the bug to Acid3. Does my comment insinuate either anger that Opera beat WebKit or that there is a conspiracy? No. It insinuates that Opera was not coding to the standards, but to the test.
For full disclosure, I asked on the Safari Blog, under the post chronicling the bug fixes that went into passing test 79, whether Safari codes to the standards or to the test.
using
@Geoff : ” It insinuates that Opera was not coding to the standards, but to the test. ”
… or both ?, but test first, to beat Safari
using
Safari was coding to the test, so I’m not sure what Geoff is saying. Apple even hard-coded a hack for a specific font in order to pass the pixel-perfect test.
using
It Works, that’s perfect!
Congratulations…
using
great success for opera team
almost done..
I’m waiting..
using
“if they were coding for standards compliance, not Acid3 compliance, they would have been the ones to submit the bug to Acid3″
Following Geoff’s logic we must conclude that if Webkit devs were honest folks and not cheaters they wouldn’t have hard-coded the fonts to be able to reach 100% ( http://ln.hixie.ch/?start=1206756775&count=1 ) …
Apple zealots: constant amusement near your internet!.
using
@Geoff: You are assuming that the test failed, or at least that part of the test failed, when Opera begun working on ACID3.
using
So who is updating Opera Watch now?
using
nice to be first!!