You may be familiar with the Acid 2 Browser Test, but the news is that an Acid 3 test in the works. Announced earlier today on John Resig's blog, a new Acid test is being created and a pre-pre-pre-alpha development version is available here
Here's an excerpt from John's post:
Traditionally, the Acid test has served as a way to get browser vendors in line by testing them on really-annoying edge cases. This can, sometimes, get people tied up in knots but it actually serves as a devious way of getting people to meet a large part of a spec.
For example, in order for a browser to have some weird padding/margin test case solved - in CSS - they must also have a working box model. So while an Acid test may not, explicitly, test for a working box model, it will be done implicitly (by testing edge cases that result from it).
With that in mind, it's time to take a look at Acid 3 which primarily focuses on technology that I find to be interesting: ECMAScript and the DOM.
Go read the full post for more information and to see just how badly the major browsers perfom on the test!
I went ahead and submitted the Acid 3 test url to browsershots.org and ran it through a few different browsers/operating systems, you can check the results here.

Delicious
Digg
StumbleUpon
Propeller
Reddit
Magnoliacom
Newsvine
Furl
Facebook
Google
Yahoo
Technorati
Icerocket
Post new comment