|
Compliant browsers If rendered correctly, Acid2 will appear as a smiley face in the user's browser, with the nose turning blue when moused over. At the time of the test's release, no browsers could render Acid2 correctly but now at least five released applications pass the test by rendering it correctly: Although the Web Standards Project web site states that iCab passes Acid2, it technically falls short by displaying a scrollbar on the viewport. (A correctly rendered test should not have a scrollbar.•) Konqueror originally had the same problem when it first was stated to have passed the test, but this issue was corrected with release 3.5.2. Non-compliant browsers Although Internet Explorer has also been moving towards better CSS compliance, its author, Microsoft, has publicly stated that Acid2 is not one of their primary focuses, and that Internet Explorer 7 does not pass the test.• The programmers of the Mozilla family of browsers (including Mozilla Suite, Firefox, Seamonkey, Camino Mac OS X, and Netscape 6+) have been making gradual efforts to have their browsers pass the Acid2 test, but it is unclear when this will take place. The delay is due to fundamental architecture work that has to be done to the Gecko rendering engine to support the changes that Acid2 requires.• It's unlikely that an end-user release that supports Acid2 will appear before 2007. A Firefox 3.0 (Minefield) branch does exist that passes the Acid2 test*. It will be merged into Firefox 3 proper. Passing conditions The test has been designed so that it is only valid with browser's default settings. Changing font sizes, zoom level, applying user stylesheets etc can break the display of the test. This is expected and is not relevant to a browser's compliance. Ian Hickson, the author of the test, has provided WaSP with clarifications about the Acid2 test and how things should behave.• The following browser settings and user actions may affect the rendering of Acid2 page without bearing on the browser's compliance: Also, the public release of Opera has some bugs revealed by testing Acid2 under non-standard conditions: However, these bugs don't mean that Opera doesn't pass Acid2 because they require testing under non-standard conditions, which makes the test invalid. Timeline of successful browsers The Acid2 test was officially announced on April 13, 2005. The following is a list of releases noting significant builds of applications that passed the test. Trivia )" screencapture 1 screencapture 2. The web site creator RapidWeaver, availiable only for the mac, also passes the Acid2 test. This can the checked by simply dragging the url of the acid 2 test into the preview pane of rapidweaver. Because of the fact that it is built using WebKit, apple's web browser the RapidWeaver preview window displays just as well as safari. See also | ||||||||||
|
| |||||||||||
 |
|
| |