Acid2

Acid2

This is the reference image for Acid2. In the real test, the nose becomes blue while the cursor is hovering over it.
URL	acid2.acidtests.org
Commercial?	No
Type of site	Web standards test
Registration	No
Available language(s)	English language
Owner	The Web Standards Project
Created by	Ian Hickson
Launched	April 13, 2005
Current status	Online

Acid2 is a test page published and promoted by the Web Standards Project to expose web page rendering flaws in web browsers and other applications that render HTML. Named after the acid test for gold, it was developed in the spirit of Acid1, a relatively narrow test of compliance with the Cascading Style Sheets 1.0 (CSS1) standard, and was released on April 13, 2005. As with Acid1, an application passes the test if the way it displays the test page matches a reference image.

Acid2 tests aspects of HTML markup, CSS 2.1 styling, PNG images, and data URIs. 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.

While at the time of Acid2's release no web browser passed the test, Acid2 was designed with Microsoft Internet Explorer particularly in mind. The creators of Acid2 were dismayed that Internet Explorer did not follow web standards, and that because of this, Internet Explorer was prone to display web pages differently from other browsers. When such a discrepancy between browsers is encountered, web developers spend time tweaking their web pages in order to make the pages be displayed correctly across different browsers. Acid2 represented a challenge to Microsoft to bring Internet Explorer into compliance with web standards, making it easier to design web pages that work as intended in any web browser.

On October 31, 2005, Safari 2.0.2 became the first browser to pass Acid2. Opera, Konqueror, Firefox, and others followed. With the release of Internet Explorer 8 on March 19, 2009, the latest versions of all major desktop web browsers now pass the test. Acid2 was followed by Acid3.

Contents 1 History 2 Microsoft's response 3 Overview of standards tested 4 Passing conditions 5 Compliant applications 5.1 Officially released 6 Non-compliant applications 7 Timeline of passing applications 8 See also 9 References 10 External links

History

Acid2 was first proposed by Håkon Wium Lie, chief technical officer of Opera Software and creator of the widely used Cascading Style Sheets web standard.^[1] In a March 16, 2005 article on CNET, Lie expressed dismay that Microsoft 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 to Microsoft to design Internet Explorer 7, then in development, to achieve a greater degree of standards compliance than previous versions of Internet Explorer. The original Acid1 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, had created the first draft of the test in February 2005.^[3] Ian Hickson coded the final test in collaboration with the Web Standards Project and the larger web community.^[2][4][5][6] It was officially released on April 13, 2005^[7] and at that time, every web browser failed it spectacularly.^[8]

On April 23, 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 unpopular SGML-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 released Acid3 as a follow-up to Acid2. While Acid2 primarily tests CSS, Acid3 focuses more on JavaScript and other "Web 2.0" technologies.^[11]

Microsoft's response

In July 2005, Chris Wilson, the Internet Explorer Platform Architect, stated that passing Acid2 was not a priority for Internet 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 in Internet 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]

Unfortunately, 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 via UNC paths, named addresses without dots (like http://mysite/), and sites that bypass the proxy settings.^[21] As such, IE8 will not pass the Acid2 test if loaded in these cases.^[22]

Overview of standards tested

Acid2 tests a variety of web standards published by the World Wide Web Consortium and the Internet Engineering Task Force. With the exception of CSS 2.1, all web standards tested were codified before the year 2000.^{[23][24][25][26]} CSS 2.1 was a candidate recommendation at the time of Acid2's release,^[27] and is still a candidate recommendation as of 23 April 2009.^[28]

Specifically, Acid2 tests:^[29]

• Alpha transparency in PNG-format images: The eyes of the smiley face use alpha transparency which is part of the 1996 Portable Network Graphics specification. The alpha transparency provides an elegant way to have the eyebrows smoothly blend into the face. This was a significant issue because Internet Explorer 6, the most widely used web browser at the time Acid2 was released,^[30] did not support alpha transparency. This deficiency was rectified in Internet Explorer 7, bringing Internet Explorer in line with other web browsers in this regard.^[31]

• The object 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. Data URIs allow embedding multimedia directly into web pages rather than being stored as a separate file. Acid2 tests the most common case, where a binary image is base64-encoded into text and then that encoded text is included in a data URI in the web page. Interestingly, 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 the data 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]

• The CSS box model: This feature allows specifying dimensions, padding, borders, and margins,^[36] and was the focus of the original Acid1 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 applying table formatting without traditional HTML 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 or painted on top of each other in the correct order.

• Hovering effects: When the user moves his or her mouse over the smiley face's nose, it turns blue. This is called a hovering effect, and while it has traditionally been used for hyperlinks, 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]

Passing conditions

A passing score 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
• Using Opera's Fit to width or Small Screen Rendering modes
• Applying custom fonts, colors, styles, etc.
• User JavaScript or Greasemonkey scripts
• Enabling Internet Explorer's "compatibility view"

Compliant applications

If rendered correctly, Acid2 will appear as a smiley face below the text "Hello World!" in the user's browser, with the nose turning blue when the mouse cursor hovers over it. At the time of the test's release every browser failed it,^[8] but now a number of applications pass the test:

Officially released

• Internet Explorer, the web browser that comes with Windows
• Gecko-based browsers
  • Mozilla Firefox, a web browser for Windows, Mac OS X, and Linux
  • SeaMonkey, an Internet suite for Windows, Mac OS X, and Linux
  • Songbird, a media player and web browser for Windows, Mac OS X, and Linux
  • Camino, a web browser for Mac OS X
  • Mozilla Thunderbird, an email client for Windows, Mac OS X, and Linux
  • Firefox for mobile, a web browser for mobile devices
  • Miro, an RSS aggregator, BitTorrent client, web browser and media player
  • Mozilla Sunbird, a calendar application for Windows, Mac OS X, and Linux
  • Spicebird 0.8, a personal information manager for Windows, Mac OS X, and Linux
  • WebRunner (formerly Prism), a web application platform for Windows, Mac OS X, and Linux
• WebKit- and KHTML-based browsers
  • Safari, the web browser included in Mac OS X and available for Windows
  • Google Chrome, a web browser for Windows, Mac OS X, and Linux
  • Konqueror, a web browser for Linux
  • OmniWeb, a web browser for Mac OS X
  • Shiira, a web browser for Mac OS X
  • iCab, a web browser for Mac OS X
  • Epiphany, the official GNOME web browser
  • Midori, the official Xfce web browser
  • The Google Earth integrated web browser
• Presto-based browsers
  • Opera, a web browser for Windows, Mac OS X, Linux, BSD and Solaris with mobile versions for all mobile phones, tablets and all Apple products like iPad
  • The Internet Channel, a version of the Opera browser for the Nintendo Wii game console.
• Prince, an XML-to-PDF converter for Windows, Mac OS X, and Linux

Non-compliant applications

Even though Opera Mini is based on the same rendering engine as Opera for personal computers, it does not pass the Acid2 test.^[41][42] This is because Opera Mini intentionally reformats web pages to try to make them more suitable for devices with small screens.^[38][43][44]

Timeline of passing applications

The following is a list of releases noting significant releases of applications that passed the test. New applications that have passed Acid2 since their first official release are not included in the timeline.

Date	Browser	Availability	Notes
27 April 2005	Safari	private build[45]
18 May 2005	iCab	private build[46]	This build was made available to registered iCab users on May 20, 2005.
4 June 2005	Konqueror	private build[47]
6 June 2005	iCab	public build[46]	Whether this version of iCab truly passes the test or not was questioned because it displays a scrollbar on the test page.[48] The CSS specification states that Acid2 correctly rendered should not have a scrollbar,[49] but also says that "there may exist valid reasons in particular circumstances" to ignore this requirement.[50][51]
6 June 2005	Safari	source code available[52]	WebKit, the underpinnings of Safari, was made open source on June 6, 2005. When Safari was run with this latest version of WebKit, it passed the Acid2 test.
31 October 2005	Safari 2.0.2	official release[53][54]	Included in Mac OS X 10.4.3. First officially released web browser to pass test.
29 November 2005	Konqueror 3.5	official release[55]	First Linux-compatible browser to pass the test, although it did not hide the scrollbar.
7 December 2005	Prince 5.1	official release[56]	First non-web browser to pass test.
10 March 2006	Opera 9 Development build 8249	public weekly build[57][58]	First Microsoft Windows-compatible browser to pass the test and also the first Linux-compatible browser to pass the test including hiding the scrollbar. A public beta was released on April 20, also successful.[59][60]
28 March 2006	Konqueror 3.5.2	official release[61]	Updated to hide the scrollbar.[62][63]
11 April 2006	Mozilla Firefox	public nightly build[64]	The "reflow refactoring" nightly builds, whose code was branched from the Gecko 1.9/Firefox 3.0 trunk, pass Acid2.
24 May 2006	Opera Mobile for Symbian OS	private build[65]	First mobile browser to pass test.
20 July 2006	OmniWeb 5.5 beta 1	public build[66][67][68]	OmniWeb switches its rendering engine to WebKit, the same rendering engine used in Safari which already passed the Acid2 test
20 June 2006	Opera 9.0	official release[69]
4 July 2006	Obigo Browser	private build[70]	Second mobile browser to pass test.
17 August 2006	iCab 3.0.3	official release[71]	First public release that hides the scrollbar.
6 September 2006	OmniWeb 5.5	official release[66]
8 December 2006	Mozilla Firefox, Camino, SeaMonkey	public nightly build[72]	Reflow refactoring branch is merged into main Gecko trunk. Firefox, Camino, and SeaMonkey trunk builds now pass Acid2.
5 March 2008	Internet Explorer 8 Beta 1	public build[73]	Beta 1 passes the test when hosted at www.webstandards.org, but fails the test when hosted at webstandards.org or acid2.acidtests.org.[18]
17 June 2008	Mozilla Firefox 3.0	official release[74][75]
27 August 2008	Internet Explorer 8 Beta 2	public build[76]	Beta 2 and later pass the test unless it is hosted from the Intranet Zone.[20][22]
2 September 2008	Google Chrome 0.2 beta	public build[77]
14 October 2008	Flock 2.0	official release[78]
11 December 2008	Google Chrome 1.0	official release
19 March 2009	Internet Explorer 8	official release[79]
27 October 2009	SeaMonkey 2.0	official release[80]
18 November 2009	Camino 2.0	official release[81]
24 June 2010	Spicebird 0.8	official release[82]

See also

• Comparison of layout engines

References

External links

• Acid2 Test
• Acid2 test information
• Acid 2 in major browsers
• The Web Standards Project's collection of Acid tests
• April 13, 2005 Web Standards Project press release
• CNET article proposing the Acid2 test
• Acid2 timeline

Acid tests by the Web Standards Project Acid1 Acid2 Acid3