Acid3

The Acid Test ( engl. acid, acid ') are test sites for testing of web browsers and similar applications on their conformity to the standards of the World Wide Web Consortium (W3C).

The first Acid Test in 1998 was developed by Todd Fahrner, and subsequently included in the official CSS 1.0 test suite of the World Wide Web Consortium. The subsequent tests " Acid2 " ( 2005) and " Acid3 " (2008) were developed and published by the Web Standards Project ( WaSP ). The tests are considered by most browser manufacturers as a hurdle above which illustrates the good support of web standards of the World Wide Web Consortium.

• 3.1 Tested Standards
• 3.2 Application Compatibility
• 3.3 Comparison of different browsers 3.3.1 Desktop Browser
• 3.3.2 Mobile Browser

Acid

Acid, also called Boxacid, was developed and released in October 1998 by Todd Fahrner. Today was the first Acid Test plays almost no role in any common graphical web browser for some time now pass this test already. In 1999, the Acid Test is included in the official CSS 1.0 test suite of the World Wide Web Consortium. The original Acid - test showed for Ian Hickson, the developer of the browser tests " Acid2 " and " Acid3 ", the central inspiration to develop its own browser tests.

Unlike the browser tests previously used to verify the interoperability of web browsers with CSS 1.0, combines the Acid test a large number of different tests on a page. To check the renderings the reference rendering is inspired by the browser tests by Braden McDaniel, used, which must be the same in the web browser with the issue.

The Mozilla Firefox or the Mozilla Application Suite, Acid existed for an early beta version. With version 6 of Internet Explorer finally a change in the interpretation of the width declaration of CSS was introduced, whereby the Internet Explorer since then also is able to pass the test. Unlike the browser by Mozilla and Microsoft who was at that time still relevant Netscape Navigator 4 was hopelessly overwhelmed with the test.

Acid2

Acid2 was developed by the Web Standards Project ( WaSP ) and on 12 April 2005, published in accordance with the original test " Acid" of 1998. Main reason for the development of this test was the increasing lack of support for the W3C standards by the various manufacturers of web browsers. This development led to higher costs in the development of websites and labored users of alternative browsers the appearance of the web pages in some cases substantially. Although several leading manufacturers of the suggestion of the WaSP initially were skeptical, a return takes place gradually since 2000.

Task of the test is the detection of render errors by web browser. The test uses the principles of HTML, but mainly CSS skills will be tested, as these were inadequately supported at the time of development of the most browsers. The main intention is here, the problems with the browsers emphasized that do not pass the test. All browsers, the HTML and CSS implementations are compatible with the specifications of the World Wide Web Consortium, have no difficulty in the presentation.

When designing the Acid2 tests, the developers also laid emphasis on the compatibility error. Many browsers have implemented routines for automatic error correction. However, the CSS standard prescribes that bad code is to be ignored. Therefore, the Acid2 test aware also contains incorrect code that the browser must ignore.

Tested standards

• So-called "Data URLs" - The source code of example files are included directly in the HTML source and not be called on a separate URL.
• General parsing CSS - The Acid2 test involves some faulty CSS declarations that must be ignored.
• Absolute, relative and fixed positioning of elements using CSS
• Driving over ( " hover " ) of elements - the nose of smileys is blue
• Indoor and outdoor distances of elements
• The overlapping of different elements
• With CSS realized Tables
• With CSS generated content
• The CSS inline box model
• The CSS Box Model
• Alpha blending PNG images
• The object element

Compatibility of applications

If the Acid2 test has been passed, should be a smilie with the text " Hello World!" Be visible in the browser window. If you hover the mouse over the nose of the smileys, it changes its color and becomes blue. As at the date of the test, none of the usual rendering engines was able to display the page correctly. Since March 2009, the latest versions of all the usual rendering engines pass the test.

• KHTML / WebKit Safari was in April 2005 with version 2.0.2, the first browser that could pass the Acid2 test. The necessary update to the WebKit version 10.4.3 has been an official part of Mac OS X and enables all Mac browsers that use WebKit to pass the test.
• Konqueror ( from KDE 3.5) comes from the same code base as well as Safari ( KHTML ), whereby some of the fixes to Safari were again used for Konqueror.
• iCab has version 3.0 or pass the Acid2 test. For version 4.0, iCab has been completely rewritten and is now on WebKit as the rendering engine.

• Opera was founded in March 2006 with version 9.0 the Acid2 test.

• Mozilla Firefox master the Acid2 test since published in June 2008, version 3.0.

• Windows Internet Explorer shows since March 2009, version 8.0 as the last of the major Web browsers, the correct representation of the test.

• Prince XML (version 5.1 ), an XML-to - PDF converter of YesLogic, founded in December 2005 also the test.

Acid3

Acid3 was, like its predecessor " Acid2 " from the Web Standards Project ( WaSP ) was developed. The development was started in April 2007 by Ian Hickson and finally published in February 2008. Unlike Acid2 the third Acid Test focuses on interactive websites and tests accordingly primary DOM Level 2 and ECMAScript. However, the browser for example also be checked for SVG and XML support.

In September 2011, the Acid3 test has been adapted to current developments in the browser market. This has made it easier to pass the test, so that subsequently a variety of browsers to test with a higher score to complete than before.

Tested standards

Acid3 was implemented with JavaScript and contains 100 individual tests, the " buckets " are divided into six groups, named, organized. In addition, the Acid3 test has four additional special tests.

• Bucket 1: DOM Traversal, DOM Range, HTTP
• Bucket 2: DOM2 Core and DOM2 Events
• Bucket 3: DOM2 Views, DOM2 Style and CSS 3 selectors
• Bucket 4: HTML and DOM
• Bucket 5: Tests of the Acid3 Competition (SVG, HTML, SMIL, Unicode, XML ... )
• Bucket 6: ECMAScript

In addition to the 100 individual tests must be rendered on the browser Acid3 test page also visually match the reference rendering. So need to correct for a representation and the existence of the Acid3 test and text shadow (CSS 3), downloadable fonts ( " web font " CSS 2.0 ), Base64 -encoded images support (in the form of data- URLs) and color representations in HSLA color space be. In addition, the animation of the test is to be carried out smoothly.

Compatibility of applications

When calling the Acid3 tests should be a percentage counter, each step may require a maximum of 33 ms to execute, count up to 100. This counter is based on the number of individual tests passed. In the background are colored rectangles and the text provided with shade " Acid3 ". However, the existence of all 100 individual tests is not sufficient to pass the entire test, the representation must match that of the reference renderings.

The test itself was written so that the time of publication no browser has been able to pass the test. Currently, WebKit ( Safari version 4 and Google Chrome version 3 ), Gecko (Mozilla Firefox 4) and Presto ( Opera version 10 ) is able to fully pass the test. In addition, requires the Acid3 test that all individual tests require a maximum of 33 ms to execute. In particular, test 26 here prepares many rendering engine manufacturers problems.

On April 22, 2008, Ian Hickson, the developer of the Acid3 tests, corrects an error again, which was discovered by a developer of Mozilla. This change had the effect that previous reports of the existence of the 100 individual tests no longer met by WebKit and Presto date. Meanwhile, both WebKit and Presto are again able to pass all 100 individual tests.

Mozilla Firefox and Internet Explorer reached only 97 and 95 percent respectively of the Acid3 test. In the last percentage points the implementation of SVG fonts and native SVG animation was tested. These have however been marked as obsolete already in coming versions of HTML and displaced by the introduction of WOFF and manipulation by JavaScript. Other browsers have these features implemented only very incomplete and flawed, just to pass the Acid3 test.

On September 17, 2011 Ian Hickson and Håkon Wium Lie have revised the Acid3 test. Only parts of some tests were removed or commented out, which relate to the implementation of features that are either greatly revised in the specifications in question or removed entirely or be. This mainly affects the tests with respect to DOM Events, DOM Range ( both are summarized in DOMException ), Attr objects, SVG Animation ( SMIL ), SVG fonts, XLink and DocType nodes. Due to this change, the test developer can develop the underlying and still changing specifications without having to consider the effective advertising Acid3 results into consideration.

As a result of these changes reach Firefox and Internet Explorer at the Acid3 test now also a 100/100-Resultat. With the publication of the Consumer Preview on 29 February 2012 is the Internet Explorer 10 the Acid3 test fully.

Comparison of different browsers

In the following, different browsers are compared on the basis of points accumulated. It will be called next to the most recent browser versions and the pre-release versions, from which a browser reaches this score.

Desktop browser

Mobile Browser

Acid4

Ian Hickson wanted to start with the development of Acid4, when three of the four major rendering engines ( WebKit, Gecko, Presto and Trident ) Acid3 exist in public builds. This is the case since 2011. Hickson will put in Acid4 special emphasis on SVG, CSS3 and mixed namespaces.