Jump to content

Acid3

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Spunker88 (talk | contribs) at 00:54, 26 February 2010 (Added Skyfire). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Acid3
The "reference rendering" for Acid3
Type of site
Web standards test
Available inEnglish language
OwnerThe Web Standards Project
Created byIan Hickson
URLhttp://acid3.acidtests.org

Acid3 is a test page from the Web Standards Project that checks how well a web browser follows certain selected elements from web standards, especially relating to the Document Object Model (DOM) and JavaScript.

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 subtests passed. It does not represent an actual percentage of conformance as the test does not keep track of how many of the subtests were actually started (100 is assumed). In addition to these the browser also has to render the page exactly as the reference page is rendered in the same browser. Like the text of the Acid2 test, the text of the Acid3 reference rendering is not a bitmap, in order to allow for certain differences in font rendering.

Acid3 was in development from April 2007,[1] and released on 3 March 2008.[2] The main developer was Ian Hickson, who also wrote the Acid2 test. Acid2 focused primarily on Cascading Style Sheets(CSS), but this third Acid test also focuses on technologies used on modern, highly interactive websites characteristic of Web 2.0, such as ECMAScript and DOM Level 2. A few subtests also concern Scalable Vector Graphics (SVG), Extensible Markup Language (XML), and data URIs. Controversially, it includes several elements from the CSS2 recommendation that were later removed in CSS2.1 but reintroduced in World Wide Web Consortium(W3C) CSS3 working drafts that have not made it to candidate recommendations yet.

The test

The main part of Acid3 is written in ECMAScript (JavaScript) and consists of 100 subtests in six groups called “buckets”, including four special subtests (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, CSS 3 selectors and Media Queries[4]
  • Bucket 4: Behavior of HTML tables and forms when manipulated by script and DOM2 HTML
  • Bucket 5: Tests from the Acid3 Competition (SVG,[5] HTML, SMIL, Unicode, …)
  • Bucket 6: ECMAScript

The compliance criteria require that the test is run with a browser's default settings. The final rendering must have a 100/100 score and must be pixel-identical with the reference rendering.[6] On browsers designed for personal computers, the animation has to be smooth (taking no more than 33 ms for each subtest on reference hardware equivalent to a top-of-the-line Apple laptop) as well,[7] though slower performance on a slow device does not imply non-conformance.[8]

Acid3 rendered by Fennec 1.0 alpha 1. Buckets 2, 4, and 6 pass all 16 subtests, buckets 1 and 3 pass more than 10 subtests while bucket 5 passes more than 5 subtests.

To pass the test the browser must also display a generic favicon in the browser toolbar, not the favicon image from the Acid3 web server. The Acid3 server when asked for favicon.ico gives a 404 response code but with image data in the body. This tests that the web browser correctly handles the 404 error code when fetching the favicon, by treating this as a failure and displaying the generic icon instead.[9]

As the test is run, rectangles are added to the rendered image; the color of the rectangles is decided by the number of subtests passed in the bucket. If all subtests fail in a particular bucket, its associated rendered rectangle will be invisible. If some subtests are cleared the color will change in four steps:

  • 1–5 subtests passed: Black rectangle.
  • 6–10 subtests passed: Grey rectangle.
  • 11–15 subtests passed: Silver rectangle.
  • All 16 subtests passed: Colored rectangle (red, orange, yellow, lime, blue, purple—for each of the six rectangles, respectively).

Detailed results

After the Acid3 test page is completely rendered, the capital A in the word Acid3 can be clicked to see an alert (or shift-click for a new window) explaining exactly which subtests have failed and what the error message was. In case some of the 100 tests passed but took too much time, the report includes timing results for that single test. The alert reports the total time of the whole Acid3 test.

Acid3 rendered by Firefox 3.6. Test failed
Acid3 rendered by Internet Explorer 8.0. Test failed
Acid3 rendered by XFCE Midori. Score 100, but test failed
File:Acid3detailSafari4.png
Acid3 rendered by Safari 4. Score 100, pixel perfect, timing ok, so test passed

In order to render the test correctly, user agents need to implement the CSS 3 Text Shadows and the CSS 2.x Downloadable Fonts specifications, which are currently under consideration by W3C to be standardized. This is required as the test uses a custom TrueType font, called "AcidAhemTest" to cover up a 20x20 red square. Supporting Truetype fonts however is not required by the CSS specification. A browser supporting only OpenType fonts with CFF outlines or Embedded OpenType fonts could support the CSS standard but fail the test in the Acid3 test. The glyph, when rendered by the downloaded font, is just a square, made white with CSS, and thus invisible.[10]

In addition, the test also uses Base64 encoded images, some more advanced selectors, CSS 3 color values (HSLA) as well as bogus selectors and values that should be ignored.

Development and impact

Ian Hickson started working on the test in April 2007, but development progressed slowly. In December 2007, work restarted and the project received public attention on 10 January 2008, when it was mentioned in blogs by Anne van Kesteren[11]. At the time the project resided at a URL clearly showing its experimental nature: "http://www.hixie.ch/tests/evil/acid/003/NOT_READY_PLEASE_DO_NOT_USE.html" That did not stop the test from receiving widespread attention within the web development community. At that time only 84 subtests were done, and on 14 January Ian Hickson announced a competition to develop the missing 16.[12]

The following developers contributed to the final test through this competition:

  • Sylvain Pasche. Subtest 66–67 (DOM).
  • David Chan. Subtest 68 (UTF-16/UCS-2).
  • Simon Pieters (Opera) and Anne van Kesteren (Opera). Subtest 71: HTML parsing.
  • Jonas Sicking (Mozilla) and Garrett Smith. Subtest 72: dynamic modification of style blocks' text nodes.
  • Jonas Sicking (Mozilla). Subtest 73: Nested events.
  • Erik Dahlström (Opera). Subtest 74–78: SVG and SMIL.
  • Cameron McCormack (Batik SVG library). Subtest 79: SVG fonts.

Even before its official release, Acid3's impact on browser development was dramatic. WebKit in particular made progress; in less than a month their score rose from 60 to 87.[13]

The test was officially released on 3 March 2008.[2] A guide and commentary was expected to follow within a few months[13], however, as of May 2009 it has not yet been released. The announcement that the test is complete means only that it is to be considered "stable enough" for actual use. A few problems and bugs were found with the test, and it was modified to fix them.[14][15] On 26 March 2008—the day both Opera and WebKit teams announced a 100/100 score—developers of WebKit contacted main Acid3 developer Ian Hickson about a critical bug in the Acid3 that presumably may have forced a violation of the SVG 1.1 standard to pass. Hickson proceeded to fix it with the help of Cameron McCormack, member of W3C's SVG Working Group.[16][17]

By the end of March 2008, early development versions of the Presto[18][19] and WebKit[17] layout engines (used by Opera and Safari respectively, among others) scored 100/100 on the test and rendered the test page correctly. At the time, no browser using the Presto or WebKit layout engines passed the performance aspect of the test. On 14 March 2009, Iris Browser 1.1.4, a WebKit-based mobile browser, became the first public release of a web browser to pass Acid3,[20][21] and on 7 June, iCab 4.6 for Mac OS X was unofficially announced as the first official release of a desktop browser to pass the test;[22][23] Safari 4, also based on WebKit, passed the next day,[24] although a development version had already passed the previous September.[25][26] By October, Epiphany, another WebKit-based browser, also passed.[27] In May and June, Google Chrome 2.0[citation needed] and Opera Mobile 9.7 beta[28] displayed a score of 100/100, but did not actually pass; release versions of these browsers passed fully later in the year.[citation needed][29] Security concerns over downloadable fonts delayed Chrome from passing.[30]

At the time of Acid3's release, Mozilla Firefox developers had been preparing for the imminent release of Firefox 3, focusing more on stability than Acid3 success. The resulting 3.0 release consequently gained a score of 71.[31] The performance of Firefox was improved in version 3.5, which scores 93/100, and version 3.6, which scores 94/100. The current trunk builds of Firefox score 96/100 with the default configuration and 97/100 with html5.enable set to true.[citation needed]

Microsoft, developers of the Internet Explorer (IE) browser, said that Acid3 does not map to the goal of Internet Explorer 8 and that IE8 would improve only some of the standards being tested by Acid3.[32] IE8 scores 20/100, which is much worse than all relevant competitors in their versions from the test's release, and has some problems with rendering the Acid3 test page. On 18 November 2009, the Internet Explorer team posted a blog entry about the early development of Internet Explorer 9, showing that an internal build of the browser could score 32/100 for the Acid3 test.[33]

Standards tested

The following standards are tested by Acid3:

  • DOM Level 2 Traversal (subtests 1–6)
  • DOM Level 2 Range (subtests 7–11)
  • Content-Type: image/png; text/plain (subtests 14–15)
  • <object> handling and HTTP status codes (subtest 16)
  • DOM Level 2 Core (subtests 17, 21)
  • DOM Level 2 Events (subtests 17, 30–32)
  • CSS Selectors (subtests 33–40)
  • DOM Level 2 Style (subtest 45)
  • DOM Level 2 HTML (subtest 60)
  • DOM Level 2 Views
  • ECMAScript GC (subtests 26–27)
  • Unicode 5.0 UTF-16 (subtest 68)
  • Unicode 5.0 UTF-8 (subtest 70)
  • HTML 4.0 Transitional (subtest 71)
  • HTML 4.01 Strict
  • SVG 1.1 (subtests 74, 78)
  • SVG 1.1 Fonts (subtests 77, 79)
  • SMIL 2.1 (subtests 75–76)
  • ECMAScript Conformance (subtests 81-96)
  • Data URI scheme (subtest 97)
  • XHTML 1.0 Strict (subtest 98)
  • HTTP 1.1 Protocol

Passing conditions

A passing score is only considered valid if the browser's default settings were used.

The following browser settings and user actions may invalidate the test:

  • Zooming in or out
  • Disabling images
  • Applying custom fonts, colors, styles, etc.

Also User JavaScript or Greasemonkey scripts may invalidate the test.

Browsers that pass

Note that only stable, public releases are listed here (alpha and beta versions, for example, would not qualify).

Desktop browsers

Template:WebSlice-begin

Layout engine Browser Rendering Performance
WebKit Safari 4.0 (8 June 2009)[34] Yes Yes[35]
Presto Opera 10 (1 September 2009)[29] Yes ?
WebKit Epiphany 2.28.0 (2 October 2009)[36] Yes[citation needed] ?
Google Chrome 4.0.249.78 (25 January 2010)[37] Yes Yes

Template:WebSlice-end

Mobile browsers

Note: For mobile browsers it is not possible to consider the "performance" portion of the test, as mobile browsers cannot be run on the reference hardware.

Template:WebSlice-begin

Layout engine Browser Rendering
WebKit Iris Browser 1.1.4 (14 March 2009)[20] Yes
BOLT Browser 1.6 (7 December 2009)[38] Yes
Presto Opera Mobile 9.7 (26 March 2009)[28] Yes

Template:WebSlice-end

Browsers that do not pass

Acid3 was deliberately written in such a way that every web browser failed the test at the time of its release. Many of the browser teams are actively working to improve test results.

Desktop browsers

Template:WebSlice-begin

Desktop browser progress for the Acid3 test
Layout engine Browser Screenshot of latest
release at time of
Acid3 release 		Screenshot of current release Screenshot of preview release
Gecko Mozilla Firefox
52/100
Mozilla Firefox 2.0.0.12
&
SeaMonkey 1.1.17
94/100
Mozilla Firefox 3.6
97/100
Mozilla Firefox nightly build (version 3.7a1)[39][40]
KHTML Konqueror
61/100
Konqueror 4.0.2
89/100
Konqueror 4.3.5
89/100
Konqueror version version 4.3 Beta 1 [41]
Trident Internet Explorer
14/100
Internet Explorer 7.0
20/100
Internet Explorer 8.0
32/100
Internet Explorer 9.0 Internal build[42]

Template:WebSlice-end

Mobile browsers

Template:WebSlice-begin

Mobile layout engine progress for the Acid3 test
Layout engine Major browsers Screenshot of latest release
at time of Acid3 release 		Screenshot of current release Screenshot of preview release
WebKit Mobile Safari
40/100
Mobile Safari 3.0 		File:MobileSafari v4.0 (iPhone OS 3.1.2 build 7D11).PNG
100/100 but incorrect rendering
Mobile Safari 4.0 		None
Android browser None
93/100
Android 2.0 		None
Nokia Mini Map Browser None
47/100
S60 5th Edition 		None
webOS browser None
73/100
webOS 1.3.1 		None
Presto Opera Mini None
98/100
Opera Mini 4.2.13212 (client)/4.12.998 (server)
98/100
Opera Mini 5 beta 2
Gecko Firefox for mobile None
94/100
Firefox for Maemo 1.0 		None
MicroB None 94/100 None
Skyfire None File:Acid3 skyfire.png
52/100
Skyfire 1.5 		None
BlackBerry BlackBerry Browser None File:BlackBerry5Acid3.jpg
91/100 		100/100
Windows CE Internet Explorer Mobile None
5/100
Internet Explorer Mobile 6[43] 		None
Zune HD Web browser None 5/100 None

Template:WebSlice-end

Console browsers

Template:WebSlice-begin

Acid3 compliance in game console web browsers
Layout engine Major browsers Screenshot of latest release
at time of Acid3 release 		Screenshot of current release Screenshot of preview release
NetFront Playstation3 browser None
27/100
PS3 Firmware 3.10 		None
PSP Browser None
11/100
NetFront 3.5 		None
Presto Nintendo DSi Browser None
59/100
None

Template:WebSlice-end

Other browsers

Template:WebSlice-begin

Acid3 compliance in game console web browsers
Layout engine Major browsers Screenshot of latest release
at time of Acid3 release 		Screenshot of current release Screenshot of preview release
Mozilla GRE
LLMozLib 2.01.29447 		Second Life browser
38/100
Second Life 1.23.5 		None None

Template:WebSlice-end

See also

Wikimedia Commons has media related to Acid3.

References

  1. ^ "HTML5 IRC logs: freenode / #whatwg / 20070422". April 23, 2007. Retrieved 2007-12-28.
  2. ^ a b "Acid3: Putting Browser Makers on Notice, Again" (Press release). Web Standards Project. 2008-03-03. Retrieved 2007-03-04.
  3. ^ Hickson, Ian (2008-03-03). "Comments in the source code of the test page". Web Standards Project. Retrieved 2008-02-16.
  4. ^ Lie, Håkon Wium (15 September 2009). "Media Queries". World Wide Web Consortium. Retrieved 9 February 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  5. ^ Dahlström, Erik (2008-01-22). "Getting to the core of the web". Opera Software. Retrieved 2008-02-16.
  6. ^ Hickson, Ian. "The Acid3 Test (reference Rendering)". Web Standards Project. Retrieved 9 February 2010.
  7. ^ Ian Hickson (2008-04-01). "The performance aspect of Acid3". Retrieved 2008-04-03.
  8. ^ "Acid3 Browser Test - The Web Standards Project". Web Standards Project. Retrieved 9 February 2010.
  9. ^ Maciej Stachowiak (2008-09-26). "comment to 'Full pass of Acid3'". WebKit.org. Retrieved 2009-04-29.
  10. ^ Hickson, Ian (2008-03-29). "The antialiasing controversy in Acid3". Retrieved 2009-04-30.
  11. ^ van Kesteren, Anne (2008-01-10). "Acid3". Retrieved 2008-03-04.
  12. ^ Hickson, Ian (2008-01-14). "The competition for you to come up with the best test for Acid3". Retrieved 2008-03-04.
  13. ^ a b Hickson, Ian (2008-03-04). "Moebius (announcement of the completion of the test)". Retrieved 2008-03-04.
  14. ^ Ian Hickson. "Tests that are never quite finished". Retrieved 2008-03-30.
  15. ^ Ian Hickson (2008-04-22). "Media queries and performance in Acid3 (and an error on my part)". Retrieved 2008-04-24.
  16. ^ Ian Hickson. "Last minute changes to Acid3". Retrieved 2008-03-30.
  17. ^ a b Maciej Stachowiak (2008-03-26). "WebKit achieves Acid3 100/100 in public build". WebKit.org. Retrieved 2008-03-26.
  18. ^ Tim Altman (March 2008). "Opera and the Acid3 Test". Opera Software. Retrieved 2008-03-28.
  19. ^ Lars Erik Bolstad (March 2008). "Public Acid3 build". Opera Software. Retrieved 2008-03-28. The latest post-9.5 build scores 99/100 and fails the smoothness criterion.
  20. ^ a b Torchmobile.com[dead link]
  21. ^ David K (March 15, 2009). "Iris 1.1.4 Released – More Stable and Scroll Support". Fuze Mobility. Retrieved 9 February 2010.
  22. ^ Michael, Lankton (July 28, 2009). "2009 Mac Web Browser Shootout!". ConnectedInternet.co.uk. Retrieved 9 February 2010.
  23. ^ "iCab 4.6 ships". FairerPlatform.com. June 8th, 2009. Retrieved 9 February 2010. {{cite web}}: Check date values in: |date= (help)
  24. ^ Paul Lilly (2008-09-29). "Safari Beta 4 is the First Browser to Hit a Perfect Acid3 Test Score". Maximum PC. Retrieved 2009-11-16.
  25. ^ Peterson, Adele (April 9th, 2007). "The WebKit browser engine running under the Safari browser UI". WebKit.org. Retrieved 2010-02-09. {{cite web}}: Check date values in: |date= (help)
  26. ^ Stachowiak, Maciej (September 25th, 2008). "Full Pass of Acid3". WebKit.org. Retrieved 2010-02-09. {{cite web}}: Check date values in: |date= (help)
  27. ^ Shane (October 2, 2009). "Epiphany". Retrieved 9 February 2010.
  28. ^ a b Lund Engebø, Helene (26. March 2009). "Opera Mobile 9.7 with Opera Turbo". Opera Software ASA. Retrieved 2009-07-06. {{cite web}}: Check date values in: |date= (help)
  29. ^ a b "Turbocharge your Web experience with Opera 10" (Press release). Opera Software. 2009-09-01. Retrieved 2009-09-04.
  30. ^ "Issue 231: Acid test 3 fails on chrome". Google. July 08, 2009. Retrieved 9 February 2010. {{cite web}}: Check date values in: |date= (help)
  31. ^ Mike Shaver (2008-03-27). "The missed opportunity of acid 3". Retrieved 2008-03-30.
  32. ^ Chris Wilson (March 20, 2008). "Windows Internet Explorer 8 Expert Zone Chat (20 March 2008)". Microsoft. Retrieved 2008-04-15. The ACID3 test is a collection of interesting tests, spread across a large set of standards. Some of those standards will see improvements in IE8 - in fact, IE8 already improves on IE7's score - but we are focused on the most important features and standards to make web developers' lives easier. The Acid3 test does not map directly to that goal.
  33. ^ "An Early Look At IE9 for Developers". Microsoft. November 18, 2009. Retrieved 9 February 2010.
  34. ^ "Safari - 150 features". Apple Inc. Retrieved 2009-09-03.
  35. ^ Stachowiak, Maciej (September 25th, 2008). "Full Pass of Acid3". WebKit.org. Retrieved 2009-12-07. {{cite web}}: Check date values in: |date= (help)
  36. ^ Paul, Ryan (September 24, 2009). "Linux garden gets a new GNOME with version 2.28". Ars Technica. Retrieved 2010-01-04.
  37. ^ Laforge, Anthony (January 25, 2010). "Stable Channel Update". Google. Retrieved 2010-01-25.
  38. ^ James, Scott (07 December 2009). "Bolt Browser gets Updated to Version 1.6 – Brings New Features!". BlackBerrySync. Retrieved 9 February 2010. {{cite web}}: Check date values in: |date= (help)
  39. ^ Sharp, Gavin (2008-01-02). "Bug 410460 (acid3) – Acid3 tracking bug". Mozilla. Retrieved 2010-02-09.
  40. ^ "Public Mozilla Acid3 spreadsheet". Retrieved 2008-10-18. {{cite web}}: Text "publisherGoogle" ignored (help)
  41. ^ 2008-01-30, Alex. "Bug 156947: Konqueror 4 fails Acid3 test (filed on 30 January 2008)". KDE. Retrieved 2008-03-02. {{cite web}}: |last= has numeric name (help)
  42. ^ Long Zheng (18. November 2009). "Img0130". Flickr. Retrieved 9 February 2010. {{cite web}}: Check date values in: |date= (help)
  43. ^ Graham, Flora (16 November 2009). "Alternative mobile browsers tested: Skyfire vs Opera Mobile vs Fennec vs Safari vs Internet Explorer vs BlackBerry". CNet.co.uk. Retrieved 9 February 2010.

Template:Acid tests

Retrieved from "https://en.wikipedia.org/w/index.php?title=Acid3&oldid=346407622"