Report on CSS Mobile Profile TS

Test suite of concern:
http://www.w3.org/Style/CSS/Test/Mobile/1.0/current/

I ran the HTML tests only. The difference betweenn HTML and XHTML is  
DOCTYPE, use of the appropriate name space, proper closing tags, and other  
XHTML-form-specific differences, the main tests are basically identical.

First thing that strikes me is that it is cumbersome to use this huge  
table as a starting point, navigating forth and back to/from the actual  
tests. It leads to long loading times. Can be solved by splitting up the  
table into smaller logical chunks. And on a side note, a list would be  
preferred over a table.

For some but not all tests there is means to navigate directly from test  
to test by <link rel="first/prev/etc">, making the table approach obsolete.

Some tests provide a link to the spec, <link rel="help">, but not all.

Almost all tests fit nicely into a 320x240 display, although many phones  
probably provide less screen dimensions. A couple of tests are the  
exception to that rule, due to e.g. (valid) word wrapping in paragraphs.

Virtually all tests rely of font effects; green background, green text,  
etc., ignoring monochrome-screen phones.

A couple of tests rely on having the Ahem font installed.

The pass condition of some tests, in particular float tests, could be  
improved.

The font tests test different rules/features, many of which are not  
available on a device with just a single font installed. Fantasy, cursive,  
etc., as well as many differrent weights and sizes are often unavailable.

Not all tests include valid style as this example shows:
<style type="text/css"><![CDATA[address { background-color: lime  
}]]></style>


Concluding, there is still the problem with an undefined coverage, and the  
tests need to be made consistent, they need review, and validation.

-- 
Till Halbach
Quality Assurance, Opera Software (www.opera.com)

Received on Tuesday, 27 February 2007 15:58:41 UTC