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

Re: ACTION 515 -New CSS approach

From: Sean Owen <srowen@google.com>
Date: Sat, 7 Jul 2007 17:27:13 -0400
Message-ID: <e920a71c0707071427r6fe20489o644bb77222ca1858@mail.gmail.com>
To: "Abel Rionda" <abel.rionda@fundacionctic.org>
Cc: public-mobileok-checker@w3.org

At a high level, I don't understand why we need to do much of anything
with CSS. We record the retrieval of the CSS document and its
contents, and some information about syntax errors. That's all we
need.

The only tests we conduct on CSS then look for absolute units of
measure, which is almost just regular expression matching, does not
need to be conducted in preprocessing, and is easily implemented in
Java.

What is the need then for CSS-in-XML or anything this complicated? I
remain concerned about how much complexity is increasing here.

Sean

On 7/6/07, Abel Rionda <abel.rionda@fundacionctic.org> wrote:
>
>
>
>
>
>
> This is a summary of what we  have already committed regarding CSS stuff:
>
>
>
> *So far, what was previously committed in CVS was explained in
>
>  a mail some days ago but the main points were:
>
>
>
>             -Java classes for represent CSS resources.
>
>             -Representation in moki of CSS validation info.
>
>             -Representation in moki of CSS test specific info.
>
>
>
> *As Sean said, the last point was not very correct (having an intermediate
>
> doc with mobileOK test specific info) so we tried to proceed with using java
>
> functions from XSLT (similar approach to Caching test).
>
> But we desisted from this approach because Java functions would not return
> primitives
>
> types but blocks of XML result code, which it is not a very good solution.
>
> In addition tests classes would need visibility of PreprocessorResults to
> extract CSS info
>
> (what is not contained in moki)
>
>
>
> *So this week, we (basically Miguel) go on with another different approach
> to fulfil
>
> this problem. This is a pseudo serialization of CSS in XML in the following
> format:
>
>
>
>             <styles>
>
>             <style>
>
>                <selector>a:link</selector>
>
>                <property name="color">rgb(0, 0, 204)</property>
>
>             </style>
>
>             <style>
>
>                <selector>a:visited</selector>
>
>                <property name="color">rgb(0, 0, 204)</property>
>
>             </style>
>
>
>
>       </styles>
>
>
>
> And we have modified MeasuresTest and StylesheetsSupportTest to deal with
>
> this approach and also in order to use the new result template.
>
>
>
> Any feedback on this will be welcome. J
>
>
>
> CTIC team
Received on Saturday, 7 July 2007 21:27:27 GMT

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