Acid3

Acid3
Tgkisapro · CC0 · source
Name	Acid3
Developer	Web Standards Project
Released	2008
Latest release	2008
Genre	Conformance test
License	Public domain

Acid3 is a web standards conformance test developed to assess compliance of web browsers and layout engines with web standards for HTML, DOM, ECMAScript, CSS, and SVG. Created by the Web Standards Project and implemented by developers associated with Opera Software, Apple Inc., Mozilla Foundation, and Google, the test became a high-profile benchmark in the late 2000s for browser interoperability. Acid3 influenced development priorities at organizations such as Microsoft Corporation, KDE, GNOME Foundation, and independent projects like WebKit and Gecko.

Overview

Acid3 was announced and published in 2008 by contributors from projects including Opera Software ASA, Apple Inc. engineers working on Safari, and members of the Mozilla Foundation working on Firefox. The test targeted conformance to specifications maintained by standards bodies such as the World Wide Web Consortium, the WHATWG, and the ECMA International Technical Committee 39. Acid3 quickly attracted attention from companies such as Google LLC, Microsoft Corporation, and community projects like Chromium and Konqueror, and was cited in coverage by outlets including The New York Times, Wired, and ZDNet.

Test Design and Components

Acid3 integrates assertions derived from formal documents published by the World Wide Web Consortium and WHATWG and exercises implementations of DOM Level 2 Core, DOM Level 3 Events, ECMAScript 262, CSS 2.1, CSS3, and SVG 1.1. Test sections exercise API behavior observed in engines like WebKit, Blink, and Gecko, and rely on rendering behaviors described in HTML 4.01, XHTML 1.0, and draft specifications such as early CSSOM and Selectors Level 3. The suite uses scripted scenarios referencing documents and examples from authors and implementers associated with Apple WebKit team, Opera Software ASA developers, and contributors to Mozilla Developer Network. Acid3 measures pixel-perfect rendering, DOM mutation ordering, event model semantics, and memory handling under conditions similar to workloads discussed at conferences like The International World Wide Web Conference and Google I/O.

Browser Compliance and Results

Early adopters including Safari on Mac OS X and builds of Opera achieved high scores soon after release, prompting rapid engineering responses from teams at Mozilla Corporation and Microsoft Corporation to address failures reported by Acid3. Google Chrome and the Chromium project incorporated fixes in V8 and Blink that improved scores; similarly, Firefox and SeaMonkey tracked regressions and implemented patches in Gecko that were discussed on mailing lists such as Mozilla Developer Network forums. Scores were publicized on blogs by developers at Opera Software ASA and Apple Inc. and aggregated by community sites run by contributors to Slashdot, Hacker News, and Stack Overflow. Major releases of Internet Explorer and engines used by Edge included compatibility work influenced by Acid3 results, and the test became part of comparative coverage alongside benchmarks like SunSpider and Kraken.

Historical Impact and Legacy

Acid3 accelerated alignment of mainstream browsers with specifications promoted by the World Wide Web Consortium and WHATWG, shaping implementation roadmaps at Mozilla Foundation, Apple Inc., Google LLC, and Microsoft Corporation. The test contributed to increased cross-project collaboration among developers from Opera Software ASA, WebKit developers, and the Chromium community, and influenced documentation on sites such as MDN Web Docs and technical postings by engineers at Red Hat and Canonical. Acid3 also inspired subsequent test suites and continuous integration practices used in projects like Khronos Group-backed conformance tests, and it is referenced in academic work at institutions like MIT, Stanford University, and University of Cambridge studying web interoperability.

Technical Criticisms and Limitations

Critics within communities including W3C working groups and independent bloggers at Ars Technica and Slashdot argued that Acid3 prioritized a snapshot of draft specification behavior over long-term stability, leading to ambiguities for implementers in Mozilla and WebKit ecosystems. Some engineers at Microsoft Research and contributors to ECMA International noted that pixel-perfect requirements and reliance on specific rendering engines encouraged hacks in JavaScript engines such as V8 and SpiderMonkey rather than robust architectural changes. Others from organizations like Red Hat and Canonical highlighted that Acid3 did not cover newer work on HTML5 multimedia, WebGL, or emerging Service Worker patterns, limiting its relevance as specifications evolved. The design prompted discussions at forums such as IETF meetings and panels at conferences like CES and SXSW about the role of conformance tests versus long-term specification stewardship.

Category:Web standards tests