|
The Acid3 test is a web test page from the Web Standards Project that checks a web browser's compliance with elements of various web standards, particularly the Document Object Model (DOM) and JavaScript. If the test is successful, the results of the Acid3 test will display a gradually increasing fraction counter below a series of colored rectangles. The number of subtests passed will indicate the percentage that will be displayed on the screen. This percentage does not represent an actual percentage of conformance as the test does not really keep track of the subtests that were actually started (100 is assumed). Moreover, the browser also has to render the page exactly as the reference page is rendered in the same browser. Like the text of the Acid2 test, the text of the Acid3 reference rendering is not a bitmap, in order to allow for certain differences in font rendering. Acid3 was in development from April 2007,〔(【引用サイトリンク】title=HTML5 IRC logs: freenode / #whatwg / 20070422 )〕 and released on 3 March 2008. The main developer was Ian Hickson, a Google employee who also wrote the Acid2 test. Acid2 focused primarily on Cascading Style Sheets (CSS), but this third Acid test also focuses on technologies used on modern, highly interactive websites characteristic of Web 2.0, such as ECMAScript and DOM Level 2. A few subtests also concern Scalable Vector Graphics (SVG), Extensible Markup Language (XML), and data URIs. Controversially, it includes several elements from the CSS2 recommendation that were later removed in CSS2.1, but reintroduced in World Wide Web Consortium (W3C) CSS3 working drafts that have not made it to candidate recommendations yet. ==The test== The main part of Acid3 is written in ECMAScript (JavaScript) and consists of 100 subtests in six groups called “buckets”, including four special subtests (0, 97, 98, and 99). * Bucket 1: DOM Traversal, DOM Range, HTTP * Bucket 2: DOM2 Core and DOM2 Events * Bucket 3: DOM2 Views, DOM2 Style, CSS 3 selectors and Media Queries * Bucket 4: Behavior of HTML tables and forms when manipulated by script and DOM2 HTML * Bucket 5: Tests from the Acid3 Competition (SVG, HTML, SMIL, Unicode, …) * Bucket 6: ECMAScript The compliance criteria require that the test be run with a browser's default settings. The final rendering must have a 100/100 score and must be pixel-identical with the reference rendering. On browsers designed for personal computers, the animation has to be smooth (taking no more than 33 ms for each subtest on reference hardware equivalent to a top-of-the-line Apple laptop) as well, though slower performance on a slow device does not imply non-conformance. To pass the test the browser must also display a generic favicon in the browser toolbar, not the favicon image from the Acid3 web server. The Acid3 server when asked for favicon.ico gives a 404 response code, but with image data in the body. This tests that the web browser correctly handles the 404 error code when fetching the favicon, by treating this as a failure and displaying the generic icon instead.When the test is running, the rectangles will be added to the rendered image; the number of subtests passed in the bucket will determine the color of the rectangles. * 0 subtests passed: No rectangle shown. * 1–5 subtests passed: Black rectangle. * 6–10 subtests passed: Grey rectangle. * 11–15 subtests passed: Silver rectangle. * All 16 subtests passed: Colored rectangle (left to right: red, orange, yellow, lime, blue, purple). Note that Acid3 does not display exactly how many subtests passed in a bucket. For example, 3 subtests passing and 4 subtests passing in bucket 2 would both render a black rectangle. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Acid3」の詳細全文を読む スポンサード リンク
|