Just a few months after the announcement that Internet Explorer 8 successfully passed the Acid2 standards compliance test, the Web Standards Project (WaSP) announced last Monday that it unleashed Acid2’s successor, Acid3. Created to identify flaws in the way a browser renders its web pages, WaSP’s Acid tests throw down the gauntlet with difficult-to-display graphics written to accentuate browsers’ quirks. When the original Acid test was released in 1998, it helped reign in browser inconsistencies and insured that Internet Explorer, Netscape, and others handled HTML code according to specification – making web designers’ lives easier and ensuring the web rendered consistently in the future.
Currently, no known browser is able to correctly render the Acid3 test, which displays an animated, incrementing score counter and a series of colored boxes with some description text. Bloggers have already assembled galleries of browsers’ failing test results, with most of today’s browsers scoring between 40 and 60 on the test’s 100-point scale. The results shouldn’t be too alarming as the Acid tests have always been forward-looking in nature, and are designed to measure standards to aspire to, as opposed to what’s current. Also note that more than six months lapsed between Acid2’s release and Safari 2.02’s announcement that it was the first to pass Acid2.
News Source: DailyTech
Currently, no known browser is able to correctly render the Acid3 test, which displays an animated, incrementing score counter and a series of colored boxes with some description text. Bloggers have already assembled galleries of browsers’ failing test results, with most of today’s browsers scoring between 40 and 60 on the test’s 100-point scale. The results shouldn’t be too alarming as the Acid tests have always been forward-looking in nature, and are designed to measure standards to aspire to, as opposed to what’s current. Also note that more than six months lapsed between Acid2’s release and Safari 2.02’s announcement that it was the first to pass Acid2.
News Source: DailyTech
http://www.neowin.net/news/main/07/12/19/i...sses-acid2-test
I got IE8 installed and it passes...
Do your homework before you speak: http://blogs.msdn.com/ie/archive/2008/03/0...sing-acid2.aspx
yes it does. stop trolling
The difference is the test NOT on webstandards site uses data uri for some other domain. Thats not permitted in IE8 BY DEFAULT for security reasons.
I mean, if no current browser actually passes the test anyway; kinda makes it hard to debug the test itself!
In the end, the best web designs are the simple ones IMO.
could be, it certainly wasn't safari
could be, it certainly wasn't safari
Actually, it was Safari:
http://en.wikipedia.org/wiki/Acid2#Timelin...pliant_browsers
Firefox and IE7 both mangle it, and fail miserably. Firefox scores a 50, while IE7 scores a 12. Opera at least looks like the rendering in structure but has no color, and scores a 60.
Firefox 2: 51%
Safari: 39%
IE7: 5%
haha wow
FireFox: 59
Opera: 60
IE: 17
Safari: 90
Webkit wins, for test I used the lasted Beta versions (nighty builds)
Indeed, he said he was using nightlies - as am I. Using the latest WebKit nightly, which Safari 3.1 is supposed to include when it is released in the coming months, I also received a 90/100. As someone else (below I think) pointed out refreshing gets different numbers.... odd.
To try this out go to http://nightly.webkit.org/
As was mentioned somewhere else here, the WebKit nightly gets positions almost exactly like the reference (very slight spacing differences). The colors of the smaller boxes and one in the middle are grey though and not the bright colors they are supposed to be.
Either way, it looks like Safari might end up being the first to pass acid again. I would guess that if it's already scoring 90/100 there isn't much more work to be done to get a perfect mark, at least in comparison to IE, Firefox and Opera maxing out at 60/100.
FireFox: 59
Opera: 60
IE: 17
Safari: 90
Webkit wins, for test I used the lasted Beta versions (nighty builds)
win32 Firefox 3 nightlies have hit 67 for weeks. They pause briefly on 18.
Why include CSS3 tests in Acid3. What if the final specification is different?
weird, different scores depending on reload
Last edited by johnorien on 06 Mar 2008 - 15:25
weird, different scores depending on reload
Yes I also got different scores on reload while using a WebKit nightly... I wonder if it behaves different if some of the data is cached. But then I would think a reload *should* re-load all of the data.
In theory they should score the same since they use the same rendering engine on all platforms, but that's obviously not confirmed or tested.
Do they have some secret browser that "works"?
Do they have some secret browser that "works"?
I assume they simply code it to adhere to exact standards, though as you point out there is no way to ensure there isn't a bug in their code. I would hope that they have gone over it with a fine tooth comb before publicizing it though - that would be quite an embarrassment if they found a bug in the test because they had no browser that could properly test it in advance!
Opera 8.65 mobile (on Q9h) - 2/100
acid3 crashes my internet explorer 7
im running windows xp x64 and the 32-bit IE crashes but the 64bit passes
does anyone know whats going on?
The latest Webkit build for OS X scores an 88/100. Weird.
and why is weird?
The weird part was that refreshing the page changed the score.
Opera is the highest (Opera 9.5 latest build I have is something like 9815)
65/100
I'd check the Firefox preivew except I've got too many plugins that rely on Firefox 2.
HAHAHA
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.