Acid3 Browser Test
Acid3 is the third in a series of test pages written to help browser vendors ensure proper support for web standards in their products.
Acid3 is primarily testing specifications for “Web 2.0″ dynamic Web applications. Also there
are some visual rendering tests, including webfonts. Here is the list of specifications tested:
- DOM2 Core
- DOM2 Events
- DOM2 HTML
- DOM2 Range
- DOM2 Style (getComputedStyle, …)
- DOM2 Traversal (NodeIterator, TreeWalker)
- DOM2 Views (defaultView)
- ECMAScript
- HTML4 (<object>, <iframe>, …)
- HTTP (Content-Type, 404, …)
- Media Queries
- Selectors (:lang, :nth-child(), combinators, dynamic changes, …)
- XHTML 1.0
- CSS2 (@font-face)
- CSS2.1 (’inline-block’, ‘pre-wrap’, parsing…)
- CSS3 Color (rgba(), hsla(), …)
- CSS3 UI (’cursor’)
- data: URIs
- SVG (SVG Animation, SVG Fonts, …)
Important Notes
When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the test page without this constituting a failure in compliance.
The Acid3 test measures some performance characteristics. The test does not attempt to make any comparisons or judgments as to the performance of any hardware used, and should not be used as a hardware benchmark. If the test is run on a slow computer or device, it may run slowly or not smoothly and this does not imply non-conformance.
Questions and Feedback
Please contact us and we will respond as quickly as possible.
The Web Standards Project is a grassroots coalition fighting for standards which ensure simple, affordable access to web technologies for all.
Recent Task Force Buzz
Acid3 Passed in 23 Days!
By Kimberly Blessing | April 7th, 2008
On March 3, the Web Standards Project launched the Acid3 Browser Test. On March 26, two browser teams reported that their builds passed.
Just over a month ago, WaSP announced the Acid3 Browser Test. At the time, we knew that some of the browser development teams were aggressively working to pass the test. What we didn’t know was how long it would take for a browser to pass the test.
“When we released Acid2, the first browser passed it in about a fortnight. Acid3 is orders of magnitude more complicated. I really didn’t expect to see passing browsers this side of August, let alone within a month,”
wrote Ian Hickson, the architect of the test, on his blog.
Well, now we know: It took under a month for not one but two browsers to pass the test. On March 26, the WebKit team announced that their public build produced a 100/100 result; Opera announced that they had an internal build which passed on the same day and they released the build on March 28. Congratulations to both teams!
In the past month we’ve received plenty of feedback and questions about the test. Thanks to the help of readers and browser developers, some bugs were identified and resolved. To learn more about the changes that were made as a result, read Ian’s post which lists the major changes.
More Buzz articles
| Title | Date |
|---|---|
| Acid3: Putting Browser Makers on Notice, Again. | March 3rd, 2008 |
| Acid3 nearing completion | February 5th, 2008 |
| What’s the best test for Acid3? | January 16th, 2008 |