< [index] >
These images should be identical:%(expected)s
# FF trunk doesn't do onload in object, so use iframe instead #index.frame.item: |- # index.frame.item: |- index: |
Last updated: %(updated)s by Philip Taylor.
Annotated specification (based on Web Applications 1.0 Working Draft — 28 August 2007)
Test results for some browsers, created semi-automatically via the report generator.
You may want to download the source code/data (e.g. to create an offline copy of the tests).
For each test, a green background indicates success, red indicates failure, blue indicates a need to manually confirm the output is as expected.
The versions in the report generator are the most visually minimalist. The category links below show the actual and expected renderings, and any error messages. The individual test links have links to relevant parts of the specification and extra notes.
Some of the tests only compare single pixels, so "success" means it avoided the obvious failure which was being tested for, rather than meaning it gave the exact expected output. Some tests make perhaps-unreasonable assumptions about exact pixel values and have too-small tolerances, and may incorrectly fail in some valid implementations or on non-32-bit displays. Some make incorrect assumptions that "should" requirements (e.g. painting gradients) are supported. Some reflect old versions of the specification, and some are just wrong. But I try to find and fix any problems, so just be a little careful for now. index.category.item: |
%d test%s expandreportgen: |
This is mainly for my own use. If anyone else wants to use it for some reason, just wait until "tests not yet loaded" and "tests not yet completed" get down to zero, then click the pass/fail button for any test it shows where it cannot work out the answer (or use the y/n keys to choose for the magenta-highlighted case), then use the buttons at the bottom to collect all the results. (WebKit has several problems with this, so it is harder to work out how to use this there.)