W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > July 2008

Various approachs to bug 5890

From: Miguel Garcia <miguel.garcia@fundacionctic.org>
Date: Mon, 28 Jul 2008 16:21:41 +0200
Message-ID: <09700B613C4DD84FA9F2FEA52188281903EC54CE@ayalga.fundacionctic.org>
To: "public-mobileok-checker" <public-mobileok-checker@w3.org>


There is a remaining css related bug, this is bug 5890 - Carriage
returns in CSS Styles not correctly handled. Currently the checker is
processing CSS line by line but is correct to write a carriage return in
the middle of a style like

p { font 
bold italic 
 12px Palatino, serif }

(I haven't checked if the CSS specification really allows this kind of
syntax but the css validator doesn't trigger any error on the previous

We have thought 3 possible solutions:

1) Process all CSS code in all together instead of line by line. It will
be quite fast to implement this approach but the drawback is that will
lose the line number of the error.

2) Currently we are searching for "property:absolute_value", that is the
property and the value must be in the same line. We could change the
regular expressions used to detect the property and the absolute values
so no linked property:value is required, just search for each token

3) Change all CSS process and implement a SAC based solution. The main
problem is the time needed to make such changes and with summer and
holidays upon us the checker could be delayed until the first or the
second week of September.

We think that the best option is the first. Taking into account that
some other errors aren't either reporting its line number, removing the
line number for CSS error it will not be a big difference.

The second option is more a workaround than a real fix and we are
lacking enough time to choose the third one. 

Any other thoughts, or any point we are missing?

Miguel & Abel
Received on Monday, 28 July 2008 14:22:25 UTC

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