Re: ISSUE-231: MINIMIZE should take into account whitespace in CSS[mobileOK Basic tests]

ISSUE-231 -- need a resolution on this.

I see that either we conclude...
- that defining exactly how to handle this is tricky enough that it
should be deferred to mobileoK Basic 1.1, as it will be a substantive
change
- that we can easily define whitespace in CSS and can add a
"clarification" that this should be checked at least, though I think
that's pushing it since it is specifically left out now
- leave any change to mobileOK Basic 1.1 as it would be substantive

I feel like we should to the latter, all things considered.

On Jan 18, 2008 7:59 AM, Jo Rabin <jrabin@mtld.mobi> wrote:
> Some morphic resonance at work in Dom and my simultaneous replies ... I agree with Dom that specifying this accurately is a reasonable amount of work (e.g. are level 2 and 3 rules extraneous?).
>
> Jo
>
>
>
> > -----Original Message-----
> > From: Dominique Hazael-Massieux [mailto:dom@w3.org]
> > Sent: 18 January 2008 07:42
> > To: Sean Owen
> > Cc: Jo Rabin; Mobile Web Best Practices Working Group WG
> > Subject: Re: ISSUE-231: MINIMIZE should take into account whitespace in
> > CSS[mobileOK Basic tests]
> >
> >
>
> > Le vendredi 18 janvier 2008 à 00:43 -0500, Sean Owen a écrit :
> > > @media screen stylesheets would not, in theory, get downloaded, so I
> > > don't think it would be counted as overhead?
> >
> > I think Jo was thinking to a single style sheet which would contain:
> >         @media screen {
> >         [100k worth of screen-only rules]
> >         }
> >
> >         @media handheld {
> >         [1 rule]
> >         }
> >
> > I agree with the assessment that this should be counted as overhead (the
> > same way with count comments in HTML markup).
> >
> > But I think we shouldn't integrate CSS into MINIMIZE at this stage in
> > the process; I'm fairly sure there would be quite a few details to iron
> > out, and this would delay the release of the spec.
> >
> > (I think our current suggestion that this be indicated as an information
> > by tools that wish to do so is a good one - that we'll probably
> > implement the W3C checker; and it will always be time to do a mobileok
> > 1.1 where you can fail because of this if we think this is really
> > important)
> >
> > Dom
>
>

Received on Thursday, 24 January 2008 16:30:06 UTC