[Xav]

It's called Acid2. Take a look at Acid2 Browser Test - The Web Standards Project.

Here's what it says:

Quote:

Acid2: The Guided Tour Hello World! Acidman smiley face Acid2 is a test page for web browsers published by The Web Standards Project (WaSP). It has been written to help browser vendors make sure their products correctly support features that web designers would like to use. These features are part of existing standards but haven’t been interoperably supported by major browsers. Acid2 tries to change this by challenging browsers to render Acid2 correctly before shipping. Acid2 is a complex web page. It uses features that are not in common use yet, because of lack of support, and it crams many tests into one page. The aim has been to make it simple for developers and users to check if a browser p***es the test. If it does, the smiley face on the left will appear. If something is wrong, the face will be distorted and/or shown partly in red. The purpose of this do***ent is to explain how Acid2 works. The markup behind Acid2 is peculiar in that it attempts, on one single page, to test many different features. We do not envision or recommend that normal Web pages should be written this way, but it is appropriate for a test page. At first sight, the source code is hard to understand, but the guided tour offered in this do***ent will explain it in some detail. The guide ***umes a technical understanding of HTML, CSS and PNG. Note: Acid2 uses data URLs extensively. To allow vendors that not yet support data URLs to test with Acid2, a version without data URLs has been published. Note: When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the Acid2 page without this constituting a failure in compliance. (Added 21 July 2006) What are we testing? Acid2 tests features that web designers have been requesting. Everything that Acid2 tests is specified in a Web standard, but not all Web standards are tested. Acid2 does not guarantee conformance with any specification. After careful consideration, we have selected and are testing the features we consider most important for the future of the web. Although Acid2 was inspired by Microsoft’s announcement of IE7, it is not targeted at a specific browser. We believe Acid2 will highlight problems in all current browsers. Acid2 ***umes basic support for HTML4, CSS1, PNG, and Data URLs. The first three items on the list are included for obvious reasons: they form the backbone of web content standards. Data URLs are described in HTML4 but is less used due to lack of support. We believe data URLs are convenient and useful for web designers, and easy to add in browsers. Further, Acid2 ***umes that the browser uses a default style sheet with common values. For example, it is ***umed that all ‘div’ elements have ‘display: block’. Finally, the test ***umes a pixel density of 96 ppi, as per the CSS 2.1 Last Call Working Draft. For user agents that support font zooming, it also ***umes a zoom factor of 100%. The list below gives an overview of the most important additional features that are tested: * Transparent PNGs — The eyes are encoded as transparent PNGs. * The object element — The eyes of the face are attached to an object element. Being able to use object (which can have alternative content) is one of the oldest requests from web designers. * Absolute, relative and fixed positioning — Being able to position elements accurately is important for advanced page layouts. * Box model — The original Acid test focused on the CSS box model. Acid2 continues in this fine tradition by testing ‘height’, ‘width’, ‘max-width’, ‘min-width’, ‘max-height’ and ‘min-height‘. * CSS tables — There is nothing wrong with table layouts. It is a powerful layout model which makes sense on bigger screens. However, the table markup is troublesome as it ties the content to these screens. Therefore, being able to specify table layouts in CSS is important. * Margins — CSS defines accurate algorithms for how margins around elements should be calculated. * Generated content — The ability to add decorations and annotations to Web pages without modifying the markup has long been requested by authors. * CSS parsing — Acid2 includes a number of illegal CSS statements that should be ignored by a compliant browser. * Paint order — We test that overlapping content is painted in the right order. This is not a feature in itself, but a requirement for other features to work correctly. * Line heights — The Acid2 test checks a few key parts of the CSS inline box model, upon which any standards-compliant Web page depends. * Hovering effects — One of the elements in the face changes color when you hover over it. Which one? It should be noted that Acid2 is rendered in standards mode. That is, the test page includes a DOCTYPE which signals that the browser should treat the page according to standards. Vendors that are reluctant to make changes in how they render legacy do***ents can continue their current behavior in what is known as quirks mode. What should appear Acid2, when rendered correctly, consists of one line of text (Hello World) and a 14×14 grid of squares inside a containing block where a smiley face can be seen. Each square is 12px high and 12px wide. The face has a yellow background with a black facial outline around it. In this section, we will explain how all of this is created.