W3C home > Mailing lists > Public > public-wai-ert@w3.org > June 2007

RE: MobileOK review

From: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
Date: Sat, 9 Jun 2007 01:51:52 +0200
Message-ID: <09700B613C4DD84FA9F2FEA521882819020C6A1D@ayalga.fundacionctic.org>
To: "Johannes Koch" <johannes.koch@fit.fraunhofer.de>, <public-wai-ert@w3.org>


Hi,

> 3 mobileOK Basic Tests
> 
> Some tests (3.1, 3.8, 3.13, 3.15, 3.21-3.24) are like
> 
>    If xyz element exists, ...
>    If the document contains ...
> 
> (which implies at most 1 message if the condition is true)
> 
> some (3.5, 3.7, 3.9, 3.12, 3.14, 3.18, 3.19) are like
> 
>    For each xyz element, ...
> 
> (which implies a message for each condition that is true)
> 
> This could be harmonized.

Ideally, tests should provide messages for every fail or warning if we want them to be useful for tracking reasons. The problem I find here is that it looks like they have defined PASSES and FAILS as "final states" that interrupt the algorithm. Note that otherwise all the algorithms will always produce a PASS, as it's always the last instruction.


> 3.12 MINIMIZE
> 
> > Count number of white space characters in a sequence of more than one
> white space character (not counting the first), which exist outside of a
> pre, style, script element, or XML comment
> 
> So unnecessary white space in internal CSS (style elements) is not
> counted?
> 
> What about white space in style attribute values? What about white space
> in "Included Style Sheet Resources"?

Apparently they are not been taken into consideration at the moment. See resolution at [1] (Member-only)

 
> 3.21 STYLE_SHEETS_USE
> 
> > If the CSS Style contains at-rules (other than the @media at-rule),
> properties, or values that are not recognized as being valid CSS Level 1
> 2.3.9 Validity, warn
> 
> in connection with (2.3.9)
> 
> > CSS
> >
> >     A resource is considered a valid CSS resource if it conforms to the
> grammar defined in [CSS], Appendix B
> 
> The CSS grammar (used for the definitio validity) does not define
> allowed at-rules, properties and values.

My understanding is that allowed properties and values are those which are included in the CSS1 grammar. Those which are not in this grammar, with the exception of the @media rule, are the not allowed properties and values (e.g. relative, absolute and fixed positioning)

Having said that, it's also strange that at 2.3.5 they say that the CSS style must be assemble using @import rules among others, and at 2.3.6 they include in the definition of included resources @import directives in the CSS styles, but at 2.3.7 there in no mention to @import while defining included style sheets that are taken into account when calculating the page size.


[1] - [http://www.w3.org/2006/02/lc-comments-tracker/37584/WD-mobileOK-basic10-tests-20070130/1620]


Regards,
 CI.

--------------------------------------

Carlos Iglesias

CTIC Foundation
Science and Technology Park of Gijón
33203 - Gijón, Asturias, Spain

phone: +34 984291212
fax: +34 984390612
email: carlos.iglesias@fundacionctic.org
URL: http://www.fundacionctic.org
Received on Friday, 8 June 2007 23:52:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:28 GMT