Acid2 is awebpage that testsweb browsers' functionality in displaying aspects ofHTML markup,CSS 2.1 styling,PNG images, anddata URIs. The test page was released on 13 April 2005 by theWeb Standards Project. The Acid2 test page will be displayed correctly in any application that follows theWorld Wide Web Consortium andInternet Engineering Task Force specifications for these technologies. These specifications are known asweb standards because they describe how technologies used on the web are expected to function.
Acid2 was designed withMicrosoft Internet Explorer particularly in mind. The creators of Acid2 were dismayed that Internet Explorer did not follow web standards. It was prone to display web pages differently from other browsers, causing web developers to spend timetweaking their web pages. Acid2 challenged Microsoft to make Internet Explorer comply with web standards. On 31 October 2005,Safari 2.0.2 became the first browser to pass Acid2.Opera,Konqueror,Firefox, and others followed. With the release ofInternet Explorer 8 on 19 March 2009, the latest versions of all major desktop web browsers now pass the test. Acid2 was followed byAcid3.
Thesmiley face of the first version of Acid2. Due to problems in this version of the test, the nose is too close to the mouth and the text "ERROR" appears even in a standards-compliant browser.
Acid2 was first proposed byHåkon Wium Lie, chief technical officer ofOpera Software and creator of the widely usedCascading Style Sheetsweb standard.[1] In a 16 March 2005 article onCNET, Lie expressed dismay thatMicrosoft Internet Explorer did not properly support web standards and hence was not completely interoperable with other browsers. He announced that Acid2 would be a challenge toMicrosoft to designInternet Explorer 7, then in development, to achieve a greater degree of standards compliance than previous versions of Internet Explorer. The originalAcid1 test had forced browser makers to fix their applications or face embarrassment; Lie hoped that Acid2 would do the same.[2]
Lie and a colleague,Ian Hickson, created the first draft of the test in February 2005.[3] Ian Hickson coded the final test in collaboration with theWeb Standards Project and the larger web community.[2][4][5][6] It was officially released on 13 April 2005[7] and at that time, every web browser failed it spectacularly.[8]
On 23 April 2005, Acid2 was updated to fix a bug that made the mouth appear too close to the nose.[9][10] After several complaints, the test was again updated in January 2006 to remove a test for unpopularSGML-style comments that were never widely implemented. In browsers that do not implement SGML-style comments, the original test displayed the word "ERROR" on the bottom part of the face.[3]
In March 2008, Ian Hickson releasedAcid3 as a follow-up to Acid2. While Acid2 primarily tests CSS, Acid3 focuses more onJavaScript and other "Web 2.0" technologies.[11]
In July 2005,Chris Wilson, the Internet Explorer Platform Architect, stated that passing Acid2 was not a priority forInternet Explorer 7, describing the test as a "wish list" of features rather than a true test of standards compliance.[12] In December 2007, Microsoft announced that all the changes required to pass Acid2 would be made available inInternet Explorer 8, but that the changes would not be turned on by default, meaning that IE8 would not actually pass the test.[13][14] The concern was that switching to a new behavior would cause too many problems in web pages expecting Internet Explorer's old, non-compliant behavior. Then in March 2008 Microsoft released IE8 beta 1 and turned on the changes by default after all.[15] James Pratt, product manager for IE8, explained that this decision was made so that "developers can spend more time building features and cool stuff, and less time just trying to tweak their sites across different browsers."[16]
Another unresolved standards compliance issue caused IE8 beta 1 to fail if not all elements of the test were hosted from the same server.[17][18][19] In August 2008 Microsoft released IE8 beta 2, which resolved the issue.[20] As of that beta, however, standards mode is not turned on by default for pages loaded in the "Intranet Zone". This zone is active for pages loaded viaUNC paths, named addresses without dots (like http://mysite/), and sites that bypass theproxy settings.[21] As such, IE8 will not pass the Acid2 test if loaded in these cases.[22]
Alpha transparency inPNG-format images: The eyes of the smiley face usealpha transparency, which is part of the 1996 Portable Network Graphics specification. Alpha transparency blends the eyebrows into the face smoothly. This was a significant issue becauseInternet Explorer 6, the most widely used web browser at the time Acid2 was released,[30] did not support alpha transparency. This deficiency was rectified inInternet Explorer 7, bringing Internet Explorer in line with other web browsers in this regard.[31]
Theobject element: The eyes also test support of the HTML object element. The object element has been a part of HTML since HTML 4 was released in 1998,[32] yet by 2005 it still was not completely supported in all web browsers. The creators of Acid2 considered object element support important because it allows for content fallback—if an object fails to load, then the browser can display alternative (generally simpler, more reliable) content in its place.
Data URIs: The actual images that form the eyes are encoded as data URIs, which allow multimedia to be embedded in web pages rather than stored as a separate file. Acid2 tests the most common case, where abinary image isbase64-encoded into text and then that encoded text is included in a data URI in the web page. Although the IETF published the data URI specification in 1998,[25] they never formally adopted it as a standard.[33] Nonetheless, the HTML 4.01 specification references thedata URI scheme,[17] and data URI support has now been implemented in most browsers.
Absolute, relative, and fixed CSS positioning: Absolute positioning means that the web developer specifies the exact X and Y coordinates where an element is to be placed into the page. Relative positioning means that the web developer specifies an X and Y offset from the usual position of the element. Fixed positioning means that the element is placed relative to the browser window, and scrolls with the window rather than with the rest of the page.[34][35]
TheCSS box model: This feature allows the web designer to specify dimensions, padding, borders, and margins,[36] and was the focus of the originalAcid1 test.[29] Acid2 not only retests margin support but also tests minimum and maximum heights and widths, features new to CSS 2.0.
CSS table formatting: This part of CSS allows the web designer to apply table formatting without traditionalHTML table markup.
CSS generated content: Using CSS generated content, web developers can add decorations and annotations to specified elements without having to add the content to each one individually.
CSS parsing: A number of illegal CSS statements are present in Acid2 to test error handling. Standards-compliant browsers are expected to handle these errors as the CSS specification directs. This helps ensure cross-browser compatibility by making all browsers treat CSS with the same level of strictness, so that what works in one browser should not cause errors in another.
Paint order: Acid2 requires that the browser has standard paint order. That is, overlapping elements should be placed orpainted on top of each other in the correct order.
Hovering effects: When the user moves the mouse over the smiley face's nose, it turns blue. This is called a hovering effect, and while it has traditionally been used forhyperlinks, it should work on a wide variety of HTML elements.[37]
Because Acid2 is not a comprehensive test, it does not guarantee total conformance to any particular standard. A variant of the Acid2 test that does not test for data URI support is also available from the Web Standards Project.[29]
Failed Acid2 on Firefox 92.0.1. This image was zoomed in by 300% on the browser, causing errors in rendering.
A passing or failing result is only considered valid if the browser's default settings were used. Actions such as changing font sizes, zoom level, and applying user stylesheets can break the display of the test. This is expected and is not relevant to a browser's compliance.[38]
The following browser settings and user actions invalidate the test:[38][39]
Scrolling
Resizing the browser window
Zooming in or out
Disabling images
UsingOpera'sFit to width orSmall Screen Rendering modes
If rendered correctly, Acid2 will appear as asmiley face below the text "Hello World!" in the user's browser, with the nose turning blue when the mouse cursor hovers over it. By the end of March 2009, the current versions of every major web browser passed the test. However, at the time of the test's release, every browser failed it.[8] The images below illustrate the various rendering errors of the most popular browsers when Acid2 was released on 13 April 2005.
Whether this version of iCab truly passes the test or not was questioned because it displays a scrollbar on the test page.[43] The CSS specification states that Acid2 correctly rendered should not have a scrollbar,[44] but also says that "there may exist valid reasons in particular circumstances" to ignore this requirement.[45][46]
WebKit, the underpinnings of Safari, was madeopen source on 6 June 2005. When Safari was run with this latest version of WebKit, it passed the Acid2 test.
FirstMicrosoft Windows-compatible browser to pass the test and also the firstLinux-compatible browser to pass the test including hiding the scrollbar. A public beta was released on 20 April, also successful.[54][55]
^Charles (19 December 2007)."IE 8: On the Path to Web Standards Compliance – ACID 2 Test Pass Complete".Microsoft Developer Network.Microsoft. Retrieved30 August 2008.About 19 minutes and 15 seconds through the video, Alex Mogilevsky, a member of the IE team, points at a picture of the Acid2 test improperly rendered and states "The video in the bottom is an IE7 version of smiley face...What you're looking at is actually IE8. It is what it looks currently in IE8 and it will look exactly like this when we ship IE8 because we are not breaking any compatibility, and this is a compatible mode of IE8. And, uh, most of the web relies on particular behavior including particularincorrect behavior, so the incorrect behavior will still be there unless the new contentwants IE to be in standards-compliant mode, and then they will ask us, and then we will show perfectly standard picture."
^Sandfeld, Allan [carewolf] (4 June 2005)."Konqueror now passes Acid2".carewolf's blog. blogs.kde.org. Archived fromthe original on 21 June 2017. Retrieved18 July 2017.
^Wilton-Jones, Mark "Tarquin"."Notes about the scrollbar".Acid 2 in major browsers.Archived from the original on 22 January 2009. Retrieved10 January 2009.
