Web Standards Browser Test

April 14, 2005

The Web Standards Project has a new web standards test for browsers called the Acid2 test. No web browsers can currently pass the test. Here's what Firefox (1.0.2), and IE (6 sp2) did on my computer:

acid 2 test rendering

The test assumes support for HTML 4, CSS1, PNG, and Data URL's (a method to encode data such as an image). Some of the things tested include:

  • Transparent PNGs
  • The object element
  • Absolute, relative and fixed positioning
  • Box Model
  • CSS Tables
  • Margins
  • etc

Dean Edwards gives his odds on which browser will win: Safari 1/3 odds - the favorite, Opera 2/1, Firefox 5/1, IE 20/1, IE7 Patch 100/1

Related Entries

7 people found this page useful, what do you think?


Yes, I've heard the Safari developer is already fixing things. Opera has some odd quirks so I'd be suprised - but again they threw down the guantlet so they almost HAVE to make it work, and the same for Firefox - they would love to come out first and say we work with are 100% Acid2 friendly. IE7. HAHAHAHAHAHAHAHAHAHA. Not in a million years.
Do you know what happens if a browser "passes the test"? if it does not? tx.
Just curious, but if no browser can pass the test how do they know their test is validly written? They couldn't test the test could they?
Actually as it turns out Bill, a Safari developer did find a bug in the test. Something to do with the positioning of the mouth being off in the reference rendering. I'm sure they just used their noggen to figure out what it should look like, and drew a picture. But the safari guy is getting close. John, I don't think anything happens if a browser passes a test besides some publicity for the browser. As of now all of them fail it.
At Time two Web Browsers will pass the ACID2-Test, it is Safari and Konqueror. See an other Test for Web Standards on http://www.aadmm.de. Compare Web Browsers and see how they work with CSS, HTML, SVG, XHTML, XML, XSLT and more.
Today's update to Safari incorporates the webcore rendering engine which is acid 2 compliant. So the production release of Safari does now pass the test.
Thanks Karl, this is the solution I was loinokg for. I am working within the DOM via Javascript, and I was trying to create a fade effect that worked in IE, Safari, Firefox on the PC and MAC. and this was it! The key being to define them in the exact order you have them written in I was trying to do IE last, but it must be done first.Take care.

Recent Entries


did you hack my cf?