ACID3 test released

The Web Standards Project just released the final version of the ACID3 test:
<uri:http://www.webstandards.org/press/releases/20080303/>

Take your browser through the test:
<uri:http://acid3.acidtests.org/>

My results:
ie7: 12 (or on Win2k3 Server with IEESC and no plugins, 6)
saf3: 39
op9.26 (8835): 46
ff2: 50
ff3b3: 59
op9.50 (9816): 65
wk (r30628): 87


I won't keep the results updated here. Visit <uri:http://web-graphics.com/2008/03/03/the-acid3-test/> to see an updated result listing.

Which browser used by them to get 100/100 ? Also what is this wk (r30628) ?

wk is WebKit. r30628 is the build number of the nightly.


There is no browser that gets 100/100 yet. That is the reference result however, i.e. how it would look in a browser that in fact did get everything in the test right. Note that this test does not have to have a pixel perfect rendering however, because differences in fonts rendering and text layout and such are allowed.

Haha, so the IE development team just celebrated themselves for getting the future IE 8 pass the acid 2 test (http://blogs.msdn.com/ie/archive/2007/12/19/internet-explorer-8-and-acid2-a-milestone.aspx) and now a new one is out which probably takes another ten years to pass.

Well, now they have a development team at least - that's gotta speed it up compared to two guys doing only security fixes as in the ie6 times...

Or better to form an alternate to w3c and define their own standards... :D

FF2 got 49/100 for me :S

about firefox info Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

My IE6 got a 12. I wish I could uninstall.

50 on FF 2.0.0.12
12 on IE7 w/Vista
58 on FF3b3

Has anyone tried IE8 on this yet?

Hello to all our friends from Slashdot! Thanks for stopping by, and please be patient with us. I don't think we've ever had the /. effect here before... Not sure what we can do to help you out, but you're certainly welcome to join our forums and help out.

50 on FF 2.0.0.12
12 on IE7 w/Vista
http://www.jamiewest.org.uk/acid3.GIF
seriously you sure you haven't got any add ons that could affect the scoring?

http://www.jamiewest.org.uk/acid3.GIF
seriously you sure you haven't got any add ons that could affect the scoring?
I just disabled all of my add-ons(and restarted firefox), and redid the test with the same result.

wierd maybe i should check for u pdates and re-run

nope no new updates

I just ran Firefox in safemode and got a 50/100. Not sure why got the 49 rafiki.

Has anyone tried IE8 on this yet?

A user on liorean's blog posted this:
I am getting: 66 on firefox 3b5pre (today’s nightly)
17 on IE 8 beta 1

50 with uBrowser :)

http://ubrowser.com/acid3/acid3.png

Hello to all our friends from Slashdot! Thanks for stopping by, and please be patient with us. I don't think we've ever had the /. effect here before... Not sure what we can do to help you out, but you're certainly welcome to join our forums and help out.
I didn't get the purpose of this post in this thread!

I didn't get the purpose of this post in this thread!This thread got slashdotted (http://it.slashdot.org/it/08/03/05/1945202.shtml) which caused quite a few database connection problems. CF is not slashdot safe, it seems :)

This thread got slashdotted (http://it.slashdot.org/it/08/03/05/1945202.shtml) which caused quite a few database connection problems. CF is not slashdot safe, it seems :)
I can't see anything special in slashdot except a link to CF. Did you mean this caused problems here?

You haven't heard of the slashdot effect? When links get posted on slashdot, that can mean tens of thousands of visits within a few minutes. Many servers balk under the strain of serving that many requests in so short time. In particular, servers usually have problems due to limited number of simultaneous network connections or database connections. It also frequently puts sites over their transfer limits or CPU usage limits in shared hosting environments. Digg can also have that effect nowadays.

:eek: Then we must learn some anti-SEO techniques :D
Just seen the thread about /. in announcement's forum

Hello to all our friends from Slashdot! Thanks for stopping by, and please be patient with us. I don't think we've ever had the /. effect here before... Not sure what we can do to help you out, but you're certainly welcome to join our forums and help out.
It's as if you are welcoming visitors from another planet. Try the keyboard! Maybe they'll copy the notes we play and establish communication!

I think we can definitely assume Alex has effectively scared the Slashdotians away with his awkward welcome, lol :p (just messing with you :D)

At least the mooninites still visit from time to time...
http://images3.wikia.nocookie.net/uncyclopedia/images/thumb/3/35/Mooninites.jpg/180px-Mooninites.jpg

-Shane

well FF3B4 gets an impressive
67/100
well IE 8 get an appauling
17/100
both in beta stages?

In linux:
FF3B4 = 68
FF2.0.0.13 = 53
Opera alpha 1 = 57

well, just tested the old ie8 here, got a 6, 14 after i moved the mouse around the horrid mess at the top of misrendered elements

upon further testing with ie8, i'm getting values ranging from 4 to 18, depending on how it feels, coming here to report back it seems that it blew ie8's tiny little mind, scrolling's way way off, keeps returning to top at random & nothing's rendered right here anymore.... such a pity, and here i thought there was hope for microsoft yet.

Theres never going to be hope for microsoft. Ever!

http://croatiankid.com/acid3.jpg

100/100

Opera (http://labs.opera.com/news/2008/03/28/) nails it, of course.

Yes. I'm a bit surprised that Opera managed to nail it before WebKit (though WebKit nailed it in a public build before Opera did). I still believe Apple are going to be releasing a final build (or even a beta build) before Opera comes around to releasing a final (or beta) which supports it, but that's because Opera are in a late stage for the 9.50 version and probably won't be able to ship 100% ACID3 compliance in that version, instead deferring those changes until 10.0. (I might be wrong about that - Opera have a tendency to surprise even their volunteer testers with big features being added at a late stage, while other stuff is frozen long before public builds appear.)

Yes. I'm a bit surprised that Opera managed to nail it before WebKit (though WebKit nailed it in a public build before Opera did). I still believe Apple are going to be releasing a final build (or even a beta build) before Opera comes around to releasing a final (or beta) which supports it, but that's because Opera are in a late stage for the 9.50 version and probably won't be able to ship 100% ACID3 compliance in that version, instead deferring those changes until 10.0. (I might be wrong about that - Opera have a tendency to surprise even their volunteer testers with big features being added at a late stage, while other stuff is frozen long before public builds appear.)

They've already said that it won't be released in Opera 10.0, whereas with everything in WebKit they've said nothing about when it will be released. It is unlikely to be in Safari.next due to SMIL being more or less totally unimplemented (it just happens to luckily support enough for Acid3 — very little more needed to implement), which would mean it would likely be disabled in any release branches in the short future.

They've already said that it won't be released in Opera 10.0Any idea where they said that? Here's what the latest Opera Desktop Team blog entry says on the topic:Many of the Acid3 fixes we've made are still undergoing testing and further development, so you will not see Kestrel achieve the same pass rate on Acid3 for the time being. (emphasis mine). Kestrel is 9.50, and from the way that sounds, the code may actually end up in Kestrel if it turns out to not cause that many nasty regressions. (There's other interesting stuff in the pipeline - that I can't talk about because I've signed an NDA - that you're likely to see in Peregrine but that are too late for Kestrel because of regressions.)It is unlikely to be in Safari.next due to SMIL being more or less totally unimplemented (it just happens to luckily support enough for Acid3 — very little more needed to implement), which would mean it would likely be disabled in any release branches in the short future.Yes, that's the impression Maciej gave me, too.

Any idea where they said that?

Anne van Kesteren has said as much in #whatwg. That (http://krijnhoetmer.nl/irc-logs/whatwg/20080326#l-412) is one example. He's said it more than once. Similarly, the comments about WebKit come from talking to Maciej there too. You can probably dig plenty of stuff up in those logs.