W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > September 2007

Status Report

From: Abel Rionda <abel.rionda@fundacionctic.org>
Date: Mon, 24 Sep 2007 14:58:38 +0200
Message-ID: <09700B613C4DD84FA9F2FEA521882819026B2717@ayalga.fundacionctic.org>
To: "public-mobileok-checker" <public-mobileok-checker@w3.org>
Hi everybody,


We have committed some changes related to our pending work. Basically we

have introduced inline CSS support and (per our action 544 [1]) we have

Minimize test. Some comments about the changes:


*Minimize test: In order to improve method that counts extraneous
characters, we have 

 reparsed the main document in HTTPXHTMLResource class using and
suitable SAX ContentHandler

 that fulfil the counting of extraneous characters as indicated in [2]. 



*Inline CSS: We have introduced a new class InlineCSSResource to manage
this kind of styles.

 An issue regarding to CSS validation error is identifying the line of
the style in the main document.

 The approach is to reparse the DOM of the main page using Saxon in
order to obtain the line number of 

 the style. Line and style are kept together (see HTTPXHTMLResource).
This line replaces the one provided by CSSValidator (see


 However, Saxon re-parsing does not work properly (in comparison with
the re-parsing of moki document, that works fine).

 It works better if we parse it directly from the raw body of the
document. Any help with this issue will be appreciate.

 So far, we have not included JUnit tests that consider inline CSS
resources but it can be tested in [3].







[1] http://www.w3.org/2005/MWI/BPWG/Group/track/actions/544

[2] http://www.w3.org/TR/mobileOK-basic10-tests/#test_minimize

[3] http://idi.fundacionctic.org/bk/inline_css.xhtml



Received on Monday, 24 September 2007 12:58:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:19 UTC