Acid3
Acid3 is a testsuite that checks how well a web browser follows certain web standards, especially relating to the DOM and JavaScript.
It was in development from April 2007,[1] to February, 2008 by Ian Hickson, who also made the Acid2 test. Acid2 focused primarily on Cascading Style Sheets, but this third Acid test focuses also on technologies used on modern, highly interactive websites, such as ECMAScript and DOM Level 2. A few tests also concern Scalable Vector Graphics, XML and data: URIs. Only elements from specifications as of 2004 are included.[2]
When successful, the Acid3 test displays a gradually increasing percentage counter with colored rectangles in the background. The percentage displayed is based on the number of sub-tests passed.
The test
Acid3 is written in JavaScript. It is a testsuite with 100 subtests, in six groups, called "buckets", plus four special tests (0, 97, 98, and 99).[3]
- Bucket 1: DOM Traversal, DOM Range, HTTP
- Bucket 2: DOM2 Core and DOM2 Events
- Bucket 3: DOM2 Views, DOM2 Style, and Selectors (CSS 3 selectors)
- Bucket 4: HTML and the DOM
- Bucket 5: Tests from the Acid3 Competition (SVG[4], HTML, SMIL, Unicode...)
- Bucket 6: ECMAScript
Non-compliant applications
-
Acid3 as rendered by Internet Explorer 7.0 -
Acid3 as rendered by Mozilla Firefox 2.0.0.12 (Gecko 1.8 branch) on Windows -
Acid3 as rendered by Opera 9.25 -
Acid3 as rendered by Konqueror 4.0.1 Note that this score is outdated : the correct one is 60 for the KDE 4.0 release -
Acid3 as rendered by Safari 3.0.4
Compliant applications
![[icon]](/wiki/File:Wiki_letter_w_cropped.svg){kind=small} | This section needs expansion. You can help by adding to it. |
The test is on purpose written in such a way that it will fail in every web browser on its release. Accordingly as of February 2008 there are no browsers that pass the test.
The team that develop Gecko, the rendering engine used in Mozilla Firefox, have a tracking bug[5] and a public spreadsheet[6] about the status of their work regarding this test. As of late February 2008 the Firefox nightly builds pass 67 of the tests.
The team that develop WebKit, used in Safari, also have a tracking bug[7]. As of late February 2008 the Webkit nightly builds pass 87 of the tests.
The tracking bug for Konqueror was filed on 30 January, 2008.[8] Anecdotal evidence suggest that Konqueror 4.0.1 passes 62 tests, but renders the image poorly.[1]
![[1]](http://rom1dep.ifrance.com/desk/score.jpg){kind=link}
References
- ^ "HTML5 IRC logs: freenode / #whatwg / 20070422". Retrieved 2007-12-28.
- ^ "HTML5 IRC logs: freenode / #whatwg / 20071228". Retrieved 2007-12-28.
- ^ Ian, Hickson. "Comments in the source code of the test page". Retrieved 2008-02-16.
- ^ Dahlström, Erik (2008-01-22). "Getting to the core of the web". Retrieved 2008-02-16.
{{cite web}}: Check date values in:|date=(help) - ^ "Bug 410460 (acid3) – Acid3 tracking bug". Retrieved 2008-02-16.
- ^ "Google document - Acid3 spreadsheet". Retrieved 2008-02-18.
- ^ "Webkit tracking bug". Retrieved 2008-02-18.
- ^ "Bug 156947: Konqueror 4 fails Acid3 test". Retrieved 2008-03-02.