CSS Mobile Profile Test Suite

This Test Suite has been designed primarily to help implementors develop more comprehensive tests and to help authors gauge the level of support for the basics of the CSS Mobile Profile. It is based upon the W3C CSS1 Test Suite.

Table of Contents

Role of the Test Suite

This Test Suite is a key part of the CSS Mobile Profile exit criteria. For this specification to exit the CR stage, the following conditions shall be met:

  1. There must be at least two interoperable implementations implementing 'all' the features in the Mobile Profile. An implementation can implement a superset of the features and claim conformance to the profile. For the purposes of this criterion, we define the following terms:


    a row in the tables of section 3 and section 4 that has not been marked 'No' in the CSS Mobile column.


    passing the respective test case(s) in the CSS test suite, or, if the implementation is not a web browser, an equivalent test. Every relevant test in the test suite should have an equivalent test created if such a UA is to be used to claim interoperability. In addition if such a UA is to be used to claim interoperability, then there must one or more additional UAs which can also pass those equivalent tests in the same way for the purpose of interoperability. The equivalent tests must be made publically available for the purposes of peer review.


    a user agent which:

    1. implements the feature.
    2. is available (i.e. publicly downloadable or available through some other public point of sale mechanism). This is the "show me" requirement.
    3. is shipping (i.e. development, private or unofficial versions are insufficient).
    4. is not experimental (i.e. is intended for a wide audience and could be used on a daily basis.)
  2. A minimum of sixth months of the CR period must have elapsed. This is to ensure that enough time is given for any remaining major errors to be caught.

Last updated by Tapas Roy 20020325. Valid XHTML 1.0! Valid CSS!