W3C home > Mailing lists > Public > www-validator-css@w3.org > August 2002

Re: Testing the new CSS Validator

From: Sijtsche Smeman <sijtsche@wisdom.nl>
Date: Thu, 8 Aug 2002 09:58:11 +0200
Message-ID: <001801c23eb1$579dfb60$3e63a8c0@wisdom.nl>
To: "Philippe Le Hegaret" <plh@w3.org>, <www-validator-css@w3.org>

Hi all,

Like Philippe, I am working on the validator when I have time between
projects at work (outside W3C) and I try to get the validator to reflect the
most recent CSS specs. The CSS3 modules selectors, color, mobile, SVG,
backgrounds and fonts are adapted to the most recent specs and will be
tested, as Philippe said.

I didn't see the cross-requests results bug in the buglist. Philippe, could
you add it? What do I have to do to reproduce it?


----- Original Message -----
From: "Philippe Le Hegaret" <plh@w3.org>
To: <www-validator-css@w3.org>
Sent: Wednesday, August 07, 2002 5:23 PM
Subject: Testing the new CSS Validator

> Folks,
> I'll test the new CSS Validator in the CSS repository in the next 10
> days. As Sijtsche said, it does not reflect the most recent specs but it
> gives a pretty good idea. If everything is fine, we'll run the version
> on the server after that.
> Regarding bug reports, yes I know, we have a few of them to track.
> Sijtsche resolved some. So we'll see what needs to be resolved after the
> new version is on jigsaw.w3.org. The cross-request results is a bad bug
> that needs to be resolved but this one is going to be tricky since I
> don't believe that the validator is using "static" inappropriately.
> For those who are wondering why I'm not fixing the bugs, the CSS
> Validator is pretty low on my priority list in fact and I only fixed
> bugs over the week-ends generally if I have the time, and that does not
> happen so often. In terms of development, the DOM TS work is higher on
> my list and needs more of my time.
> Philippe
Received on Thursday, 8 August 2002 03:58:08 UTC

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