Acid3

Last updated

Acid3
Acid3 reference.png
The reference rendering for Acid3
Type of site
 Web standards test
Available in English
OwnerThe Web Standards Project
Created by Ian Hickson
URL acid3.acidtests.org
CommercialNo
RegistrationNo
LaunchedMarch 3, 2008;15 years ago (2008-03-03)
Current statusOnline

The Acid3 test is a web test page from the Web Standards Project that checks a web browser's compliance with elements of various web standards, particularly the Document Object Model (DOM) and JavaScript.

Contents

If the test is successful, the results of the Acid3 test will display a gradually increasing fraction counter below a series of colored rectangles. The number of subtests passed will indicate the percentage that will be displayed on the screen. This percentage does not represent an actual percentage of conformance as the test does not really keep track of the subtests that were actually started (100 is assumed). Moreover, 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, a Google employee 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 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. It includes several elements from the CSS2 recommendation that were later removed in CSS2.1,[ citation needed ] but reintroduced in World Wide Web Consortium (W3C) CSS3 working drafts that have not made it to candidate recommendations yet.

By April 2017, the updated specifications had diverged from the test such that the latest versions of Google Chrome, Safari and Mozilla Firefox no longer pass the test as written. [3] Hickson acknowledges that some aspects of the test were controversial and has written that the test "no longer reflects the consensus of the Web standards it purports to test, especially when it comes to issues affecting mobile browsers". [4]

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). [5]

The compliance criteria require that the test be 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. [8] 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, [9] though slower performance on a slow device does not imply non-conformance. [10]

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. Fennec acid3-89.png
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. [11]

When the test is running, the rectangles will be added to the rendered image; the number of subtests passed in the bucket will determine the color of the rectangles.

Note that Acid3 does not display exactly how many subtests passed in a bucket. For example, 3 subtests passing and 4 subtests passing in bucket 2 would both render a black rectangle.

Detailed results

Acid3 rendered by Internet Explorer 8.0 (before the September 2011 update of the Acid3 test). 20/100, test failed. Acid3ie8rc1.png
Acid3 rendered by Internet Explorer 8.0 (before the September 2011 update of the Acid3 test). 20/100, test failed.
The Acid3 test result on Safari 3 (above, failure) and Safari 4 (below, success) Acid3 in Safari 3 & 4.png
The Acid3 test result on Safari 3 (above, failure) and Safari 4 (below, success)

After the Acid3 test page is completely rendered, the letter '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 one 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.

Screenshot of Chromium 71 running the Acid3 test as of December 2018. Chromium 71 Acid3 Test.png
Screenshot of Chromium 71 running the Acid3 test as of December 2018.

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. [12]

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

Google employee 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. [13] 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" Despite the notice in the URL, the test received widespread attention in the web-development community. At that time only 84 subtests had been done, and on 14 January Ian Hickson announced a competition to fill in the missing 16. [14]

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

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

The test was officially released on 3 March 2008. [2] A guide and commentary was expected to follow within a few months, [15] but, as of March 2011, only the commentary had 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. [16] [17] On 26 March 2008—the day both Opera and WebKit teams announced a 100/100 score—developers of WebKit contacted Hickson about a critical bug in Acid3 that presumably allowed a violation of the SVG 1.1 standard to pass. Hickson fixed the bug with the help of Cameron McCormack, a member of W3C's SVG Working Group. [18] [19]

Chrome, Presto and WebKit based browsers

In 2008, development versions of the Presto [20] [21] and WebKit [19] [22] layout engines (used by Opera and Safari respectively) 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. [23] [24]

Google Chrome and Opera Mobile [25] displayed a score of 100/100. [26] Security concerns over downloadable fonts delayed Chrome from passing. [27]

Version 68 and later of Chrome gets a score of 97/100.

Firefox

Acid3 done on Firefox 67.0.2. Acid3 test on Firefox 67.0.2.png
Acid3 done on Firefox 67.0.2.

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. Consequently, Firefox 3 had a score of 71. [28] Firefox 3.5 scored 93/100, and Firefox 3.6 scored 94/100. Initially, Firefox 4 scored 97/100, because it did not support SVG fonts. Later, Firefox 4 scored 100/100, because the SVG font tests were removed from Acid3.

According to Mozilla employee Robert O'Callahan, Firefox did not support SVG fonts because Mozilla considered WOFF a superior alternative to SVG fonts. [29] Another Mozilla engineer, Boris Zbarsky, claimed that the subset of the specification implemented in Webkit and Opera gives no benefits to web authors or users over WOFF, and he asserted that implementing SVG Fonts fully in a web browser is hard because it was "not designed with integration with HTML in mind". [30]

On 2 April 2010, Ian Hickson made minor changes to the test after Mozilla, due to privacy concerns, altered the way Gecko handles the :visited pseudo-class. [31] [32]

Firefox 51.0a1 made a regression from 100 to 99 on 14 September 2016; Firefox 55.0a1 further regressed to 97 on 1 May 2017. [33] In Firefox Quantum versions, 63.0 received 97/100; 64.0 got 96/100, 68.1.0esr and later [34] got 97/100. Firefox versions 105.0 received 99/100 while 109.0 clocked in at 97/100. As of 121.0 it scored 97/100 on the test.

Internet Explorer

Microsoft said that Acid3 did not agree with the goal of Internet Explorer 8 and that IE8 would improve only some of the standards being tested by Acid3. [35] IE8 scored 20/100, which is much worse than all relevant competitors at the time of Acid3's release, and had 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 from the PDC presentation, showing that an internal build of the browser could score 32/100. [36]

Throughout 2010, several public Developer Previews improved Internet Explorer 9's test scores from 55/100 (on 16 March [37] ) to 95/100 (as of 4 August). [38] [39] [40] Dean Hachamovich, general manager of the IE team, argued that striving for 100/100 on the Acid3 test is neither necessary, nor desirable. He claimed that the two Acid3 failures related to features (SVG fonts and SMIL animation) that were "in transition". [41]

IE's successor, Microsoft Edge, displays a score of 97/100 under version 109.

Criticism

Early iterations of the test were criticized for being a cherry-picked collection of features that were rarely used, as well as those that were still in a W3C working draft. Eric A. Meyer, a notable web standards advocate, wrote, "The real point here is that the Acid3 test isn't a broad-spectrum standards-support test. It's a showpiece, and something of a Potemkin village at that. Which is a shame, because what's really needed right now is exhaustive test suites for specifications—XHTML, CSS, DOM, SVG." [42]

"Implementing just enough of the standard to pass a test is disingenuous, and has nothing to do with standards compliance," argued Mozilla UX lead Alex Limi, in his article "Mythbusting: Why Firefox 4 won't score 100 on Acid3." Limi argued that some of the tests, particularly those for SVG fonts, have no relation to real usage, and implementations in some browsers have been created solely for the point of raising scores. [43]

September 2011 test changes

On 17 September 2011, Ian Hickson announced an update to Acid3. In Hickson's words, Håkon Wium Lie from Opera Software and he commented out "the parts of the test that might get changed in the specs." They hoped that this change would "allow the specs to change in whatever way is best for the Web, rather than constraining the changes to only be things that happened to fit what Acid3 tested!" [44]

As a result, Firefox 4 and Internet Explorer 9 achieved a score of 100/100 on Acid3, but Internet Explorer didn't render the test properly because it did not support text-shadow until Internet Explorer 10. [45]

Standards tested

Parts of the following standards are tested by Acid3:

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:

See also

Related Research Articles

Scalable Vector Graphics (SVG) is an XML-based vector image format for defining two-dimensional graphics, having support for interactivity and animation. The SVG specification is an open standard developed by the World Wide Web Consortium since 1999.

Gecko is a browser engine developed by Mozilla. It is used in the Firefox browser, the Thunderbird email client, and many other projects.

<span class="mw-page-title-main">Firefox</span> Free and open-source web browser by Mozilla

Mozilla Firefox, or simply Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. It uses the Gecko rendering engine to display web pages, which implements current and anticipated web standards. Firefox is available for Windows 10 or later versions, macOS, and Linux. Its unofficial ports are available for various Unix and Unix-like operating systems, including FreeBSD, OpenBSD, NetBSD, illumos, and Solaris Unix. It is also available for Android and iOS. However, as with all other iOS web browsers, the iOS version uses the WebKit layout engine instead of Gecko due to platform requirements. An optimized version is also available on the Amazon Fire TV as one of the two main browsers available with Amazon's Silk Browser.

<span class="mw-page-title-main">Favicon</span> Icon associated with a particular web site

A favicon, also known as a shortcut icon, website icon, tab icon, URL icon, or bookmark icon, is a file containing one or more small icons associated with a particular website or web page. A web designer can create such an icon and upload it to a website by several means, and graphical web browsers will then make use of it. Browsers that provide favicon support typically display a page's favicon in the browser's address bar and next to the page's name in a list of bookmarks. Browsers that support a tabbed document interface typically show a page's favicon next to the page's title on the tab, and site-specific browsers use the favicon as a desktop icon.

<span class="mw-page-title-main">Browser wars</span> Competition between web browsing applications for share of worldwide usage

A browser war is a competition for dominance in the usage share of web browsers. The "first browser war," (1995–2001) pitted Microsoft's Internet Explorer against Netscape's Navigator. Browser wars continued with the decline of Internet Explorer's market share and the popularity of other browsers including Firefox, Google Chrome, Safari, Microsoft Edge and Opera.

This is a comparison of both historical and current web browsers based on developer, engine, platform(s), releases, license, and cost.

Mozilla Firefox has features which distinguish it from other web browsers, such as Google Chrome, Safari, and Microsoft Edge.

<span class="mw-page-title-main">Acid2</span> Online HTML rendering test

Acid2 is a webpage that test web browsers' functionality in displaying aspects of HTML markup, CSS 2.1 styling, PNG images, and data URIs. The test page was released on 13 April 2005 by the Web Standards Project. The Acid2 test page will be displayed correctly in any application that follows the World Wide Web Consortium and Internet Engineering Task Force specifications for these technologies. These specifications are known as web standards because they describe how technologies used on the web are expected to function.

The Web Standards Project (WaSP) was a group of professional web developers dedicated to disseminating and encouraging the use of the web standards recommended by the World Wide Web Consortium, along with other groups and standards bodies.

In computing, quirks mode is an approach used by web browsers to maintain backward compatibility with web pages designed for old web browsers, instead of strictly complying with web standards in standards mode. This behavior has since been codified, so what was previously standards mode is now referred to as simply no quirks mode.

The canvas element is part of HTML5 and allows for dynamic, scriptable rendering of 2D shapes and bitmap images. It is a low level, procedural model that updates a bitmap. HTML5 Canvas also helps in making 2D games.

<span class="mw-page-title-main">Firebug (software)</span> Web development add-on for Firefox

Firebug is a discontinued free and open-source web browser extension for Mozilla Firefox that facilitated the live debugging, editing, and monitoring of any website's CSS, HTML, DOM, XHR, and JavaScript.

<span class="mw-page-title-main">Web development tools</span> Software used to test the UI of a website or web application

Web development tools allow web developers to test, modify and debug their websites. They are different from website builders and integrated development environments (IDEs) in that they do not assist in the direct creation of a webpage, rather they are tools used for testing the user interface of a website or web application.

<span class="mw-page-title-main">Internet Explorer 9</span> Web browser for Windows released in 2011

Internet Explorer 9 or IE9 is the ninth version of the Internet Explorer web browser for Windows. It was released by Microsoft on March 14, 2011, as the ninth version of Internet Explorer and the successor to Internet Explorer 8. Microsoft released Internet Explorer 9 as a major out-of-band version that was not tied to the release schedule of any particular version of Windows, unlike previous versions. It is the first version of Internet Explorer not to be bundled with a Windows operating system, although some OEMs have installed it with Windows 7 on their PCs. Internet Explorer 9 is the last version that is called Windows Internet Explorer. The software was rebranded simply as Internet Explorer starting in 2012 with the release of Internet Explorer 10.

<span class="mw-page-title-main">Web typography</span> Publishing considerations for the Web

Web typography, like typography generally, is the design of pages – their layout and typeface choices. Unlike traditional print-based typography, pages intended for display on the World Wide Web have additional technical challenges and – given its ability to change the presentation dynamically – additional opportunities. Early web page designs were very simple due to technology limitations; modern designs use Cascading Style Sheets (CSS), JavaScript and other techniques to deliver the typographer's and the client's vision.

Animation of Scalable Vector Graphics, an open XML-based standard vector graphics format is possible through various means:

<span class="mw-page-title-main">Iris Browser</span> Windows Mobile web browser

Iris Browser is a discontinued web browser for Windows Mobile smartphones and personal digital assistants (PDAs) developed by the Torch Mobile company. The first version was released in 2008. It was one of the first mobile browsers to score a perfect 100 on the Acid3 test.

<span class="mw-page-title-main">Web Compatibility Test for Mobile Browsers</span>

Web Compatibility Test for Mobile Browsers, often called the Mobile Acid test, despite not being a true Acid test, is a test page published and promoted by the World Wide Web Consortium (W3C) to expose web page rendering flaws in mobile web browsers and other applications that render HTML. It was developed in the spirit of the Acid test by the Web Standards Project to test the relevant parts that a mobile browser needs to support. The browser has to accomplish 16 different subtests indicated by a 4 x 4 image of green or red squares.

A browser speed test is a computer benchmark that scores the performance of a web browser, by measuring the browser's efficiency in completing a predefined list of tasks. In general the testing software is available online, located on a website, where different algorithms are loaded and performed in the browser client. Typical test tasks are rendering and animation, DOM transformations, string operations, mathematical calculations, sorting algorithms, graphic performance tests and memory instructions. Browser speed tests have been used during browser wars to prove superiority of specific web browsers. The popular Acid3 test is no particular speed test but checks browser conformity to web standards.

<span class="mw-page-title-main">HTML5test</span> Web application for evaluating a browsers implementation of HTML5

HTML5test is a web application for evaluating a web browser's accuracy in implementing the web standards HTML5 and Web SQL Database, as well as the WebGL standard.

References

  1. ↑ "HTML5 IRC logs: freenode / #whatwg / 20070422". 23 April 2007. Retrieved 28 December 2007.
  2. 1 2 "Acid3: Putting Browser Makers on Notice, Again" (Press release). Web Standards Project. 3 March 2008. Retrieved 4 March 2007.
  3. ↑ "Validating a qualified name does not match browsers in a corner case · Issue #319 · whatwg/dom". GitHub. Retrieved 21 September 2019.
  4. ↑ Hickson, Ian. "Acid Tests". Archived from the original on 27 September 2009. Retrieved 7 May 2018.
  5. ↑ Hickson, Ian (3 March 2008). "Comments in the source code of the test page". Web Standards Project. Archived from the original on 18 February 2008. Retrieved 16 February 2008.
  6. ↑ Lie, Håkon Wium; Çelik, Tantek; Glazman, Daniel; van Kesteren, Anne (15 September 2009). "Media Queries". World Wide Web Consortium. Archived from the original on 11 February 2010. Retrieved 9 February 2010.
  7. ↑ Dahlström, Erik (22 January 2008). "Getting to the core of the web". Opera Software. Archived from the original on 2 February 2008. Retrieved 16 February 2008.
  8. ↑ Hickson, Ian. "The Acid3 Test (reference Rendering)". Web Standards Project. Archived from the original on 12 February 2010. Retrieved 9 February 2010.
  9. ↑ Ian Hickson (1 April 2008). "The performance aspect of Acid3". Archived from the original on 5 April 2008. Retrieved 3 April 2008.
  10. ↑ "Acid3 Browser Test – The Web Standards Project". Web Standards Project. Archived from the original on 19 January 2010. Retrieved 9 February 2010.
  11. ↑ Maciej Stachowiak (26 September 2008). "comment to 'Full pass of Acid3'". WebKit.org. Retrieved 29 April 2009.
  12. ↑ Hickson, Ian (29 March 2008). "The antialiasing controversy in Acid3". Archived from the original on 8 May 2009. Retrieved 30 April 2009.
  13. ↑ van Kesteren, Anne (10 January 2008). "Acid3". Archived from the original on 7 March 2008. Retrieved 4 March 2008.
  14. ↑ Hickson, Ian (14 January 2008). "The competition for you to come up with the best test for Acid3". Archived from the original on 8 March 2008. Retrieved 4 March 2008.
  15. 1 2 Hickson, Ian (4 March 2008). "Moebius (announcement of the completion of the test)". Archived from the original on 8 March 2008. Retrieved 4 March 2008.
  16. ↑ Ian Hickson. "Tests that are never quite finished". Archived from the original on 30 March 2008. Retrieved 30 March 2008.
  17. ↑ Ian Hickson (22 April 2008). "Media queries and performance in Acid3 (and an error on my part)". Archived from the original on 25 April 2008. Retrieved 24 April 2008.
  18. ↑ Ian Hickson. "Last minute changes to Acid3" . Retrieved 30 March 2008.
  19. 1 2 Maciej Stachowiak (26 March 2008). "WebKit achieves Acid3 100/100 in public build". WebKit.org. Archived from the original on 28 March 2008. Retrieved 26 March 2008.
  20. ↑ Tim Altman (March 2008). "Opera and the Acid3 Test". Opera Software. Archived from the original on 28 March 2008. Retrieved 28 March 2008.
  21. ↑ Lars Erik Bolstad (March 2008). "Public Acid3 build". Opera Software. Archived from the original on 30 March 2008. Retrieved 28 March 2008. The latest post-9.5 build scores 99/100 and fails the smoothness criterion.
  22. ↑ Paul Lilly (29 September 2008). "Safari Beta 4 is the First Browser to Hit a Perfect Acid3 Test Score". Pcgamer. Maximum PC . Retrieved 16 November 2009.
  23. ↑ Peterson, Adele (8 April 2007). "The WebKit browser engine running under the Safari browser UI". WebKit.org. Retrieved 9 February 2010.
  24. ↑ Stachowiak, Maciej (25 September 2008). "Full Pass of Acid3". WebKit.org. Retrieved 9 February 2010.
  25. ↑ Lund Engebø, Helene (26 March 2009). "Opera Mobile 9.7 with Opera Turbo". Opera Software ASA. Archived from the original on 2 June 2009. Retrieved 6 July 2009.
  26. ↑ "Turbocharge your Web experience with Opera 10" (Press release). Opera Software. 1 September 2009. Archived from the original on 30 May 2012. Retrieved 4 September 2009.
  27. ↑ "Issue 231: Acid test 3 fails on chrome". 8 July 2009. Retrieved 9 February 2010.
  28. ↑ Mike Shaver (27 March 2008). "The missed opportunity of acid 3". Archived from the original on 29 March 2008. Retrieved 30 March 2008.
  29. ↑ Robert O'Callahan (3 June 2010). "Not Implementing Features Is Hard". Archived from the original on 6 August 2011. Retrieved 15 December 2010.
  30. ↑ Limi, Alexander (25 January 2011). "Mythbusting: Why Firefox 4 won't score 100 on Acid3" . Retrieved 20 September 2011.
  31. ↑ Baron, David (9 March 2010), Preventing attacks on a user's history through CSS :visited selectors, Mozilla, archived from the original on 5 April 2010, retrieved 8 April 2010
  32. ↑ Hickson, Ian (2 April 2010), Acid3 update for :link/:visited privacy changes , retrieved 7 April 2010
  33. ↑ chrisjone (18 October 2017). "1409813 - Firefox Quantum 57.0b9 (64-bit) (Linux) Fails Acid 3 Test". Bugzilla. Retrieved 23 December 2018.
  34. ↑ Last checked on 86.0 beta 5, 02.04.2021
  35. ↑ Chris Wilson (20 March 2008). "Windows Internet Explorer 8 Expert Zone Chat (20 March 2008)". Microsoft. Archived from the original on 20 April 2008. Retrieved 15 April 2008. 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.
  36. ↑ "An Early Look At IE9 for Developers". Microsoft. 18 November 2009. Archived from the original on 8 February 2010. Retrieved 9 February 2010.
  37. ↑ The Web Standards Project's Acid3 Test Archived 2010-08-06 at the Wayback Machine , Microsoft. For IE 9's First Developer Preview.
  38. ↑ The Web Standards Project's Acid3 Test Archived 2010-08-06 at the Wayback Machine , Microsoft. For IE 9's 2nd Developer Preview.
  39. ↑ The Web Standards Project's Acid3 Test Archived 2010-08-14 at the Wayback Machine , Microsoft. For IE 9's 3rd Developer Preview.
  40. ↑ The Web Standards Project's Acid3 Test Archived 2010-03-22 at the Wayback Machine , Microsoft. For IE 9's 4th Developer Preview.
  41. ↑ "Microsoft releases final IE9 preview, beta due in September". ZDNet. 26 August 2010. Archived from the original on 2 December 2010. Retrieved 9 November 2010.
  42. ↑ "Acid Redux". 22 March 2008. Archived from the original on 6 March 2010. Retrieved 21 March 2010.
  43. ↑ "Mythbusting: Why Firefox 4 won't score 100 on Acid3". 25 January 2011. Archived from the original on 26 January 2011. Retrieved 25 January 2011.
  44. ↑ "Ian Hickson announces Acid3 modifications". 17 September 2011. Archived from the original on 12 October 2011. Retrieved 17 September 2011.
  45. ↑ "Acid3 Test Simplified; All Modern Browsers Score 100". 20 September 2011. Retrieved 7 June 2013.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.