![[ICO]](/icons/blank.gif){kind=icon}
![[PARENTDIR]](/icons/back.gif){kind=icon}
![[TXT]](/icons/text.gif){kind=icon}
![[IMG]](/icons/image2.gif){kind=icon}
![[ ]](/icons/unknown.gif){kind=icon}
![[DIR]](/icons/folder.gif){kind=icon}
| Name | Last modified | Size | Description |
|---|---|---|---|---|
| Parent Directory | - | ||
| README.html | 2007-04-25 10:07 | 2.3K | |
| template.svg | 2007-04-22 01:42 | 396 | |
| template.xbl | 2007-04-22 01:42 | 46 | |
| template.xht | 2007-04-22 01:42 | 387 | |
| tests/ | 2007-07-10 15:54 | - | |
This document describes the structure of and the procedures for the XBL 2.0 test suite.
Test files should generally follow the same guidelines set forth in the CSS2.1 Test Case Authoring Guidelines. The following templates should be used for the test files:
The actual tests are in the tests directory.
XBL 2.0 makes no requirements on a particular scripting language to be used, however certain sections have conformance requirements for ECMAScript and CSS. Thus for practical reasons, ECMAScript and CSS are assumed to be supported.
At the time of writing, there are vague plans to implement XBL 2.0 in Firefox and Batik some time in the future, and there exists an experimental JavaScript implementation. Taking into account that it is likely that the most common use of XBL 2.0 is for binding elements in an HTML page, that some tests will be testing the inclusion of an XBL subtree in an XML document, and that Batik is an SVG-only user agent, all tests that can apply to any target language must have both an XHTML 1.0 Strict and an SVG 1.1 version. As much as possible, the actual XBL should be in a separate document to simplify the XHTML and SVG “harness” documents.