RE: Tomorrow's Task Force Call

 

Hi,

We (all three :-() can 't attend today 's call but we are sending a mail
explaining

CSS stuff for discussion on the list.

 

Regards,

Abel.

________________________________

De: public-mobileok-checker-request@w3.org
[mailto:public-mobileok-checker-request@w3.org] En nombre de Jo Rabin
Enviado el: martes, 07 de agosto de 2007 6:10
Para: public-mobileok-checker
Asunto: RE: Tomorrow's Task Force Call

 

I don't know how many people are actually around tomorrow, Laura. I will
try to be on the call, but I think that most people (including me) are
on vacation.

 

In respect of CSS, I agree that we need to have a clearer idea of what
we are trying to do, and think about how we should do it following from
that. I am a bit concerned, for example, that things like illegal CSS 1
selectors haven't been stirred properly into the mix yet - though I
haven't looked closely. I think it would be a good idea to write down in
a non-programmatic way what we think we are doing.

 

I'm all for your making a start on the HTTP request / response stuff.

 

All best

Jo

 

________________________________

From: public-mobileok-checker-request@w3.org
[mailto:public-mobileok-checker-request@w3.org] On Behalf Of Laura
Holmes
Sent: 06 August 2007 21:50
To: public-mobileok-checker
Subject: Tomorrow's Task Force Call

 

Hi all, 
I just wanted to lay out an agenda for some of the things I'd like to
discuss on the call tomorrow. Following at discussion about your
September F2F, I'd really like to hash out the details of our final CSS
implementation. It'd be really great if those who have contributed to
the development of the CSS->XML parser were present. 

Here's some of the issues:

1) What is the status of the CSS->XML parser?
         There still isn't support for:
             - recognizing @import tags
             - parsing out the values defined in properties into usable
values ( i.e. url() and the actual url, 10px)
         It'd be great to establish how much work this would take to
change before we make final decisions.
2) Discuss arguments for and against testing css with regular
expressions 
         I've already implemented retrieval of references to other
external stylesheets and images (and just recently added the code to CVS
in CSSUtils)

Just for your reference, we'll need to consider:
- external, embedded, and inline style sheets
- external resources
- parsing of dimensions for positioning
- identification of all the elements mentioned in:
http://www.w3.org/TR/mobileOK-basic10-tests/#test_style_sheets_use
and
http://www.w3.org/TR/mobileOK-basic10-tests/#test_style_sheets_support 

3) With some of the additional time I have with my internship, I'm going
to be adding in support for suite level errors. The kinds of errors that
will be included in that list are http request and response errors, like
those outlined in
http://www.w3.org/TR/mobileOK-basic10-tests/#http_response Does anyone
else have recommendations as to what else I should include in these
suite level errors? 

If you think there's anything I missed, feel free to send it out on the
list prior to the call. 

Thanks and talk to you all tomorrow!

Cheers, 
Laura