- From: Karl Dubost <karl@w3.org>
- Date: Mon, 12 Feb 2001 12:23:53 -0500 (EST)
- To: glazman@netscape.com (Daniel Glazman)
- Cc: www-style@w3.org, w3t-qa@w3.org
At 17:35 +0100 12/02/01, Daniel Glazman wrote:
>Karl Dubost wrote:
>>First of all, bravo, many examples, clear to read.
>
>Merci Karl !!! (je te dois de l'argent ?-)
On s'arrangera plus tard ;)
>>In the conformance section, we can read:
>>********************************
>>User agents must observe the rules for handling parsing errors:
>>
>>* a selector containing an invalid simple selector, an invalid
>>combinator or an invalid token is invalid.
>>* a group of selectors containing an invalid selector is invalid.
>>*********************************
>>
>>I would be very happy to see a definition of invalid. What does it
>>mean invalid in a developper point of view? It's too ambiguous.
>>So it could be good to have a clear definition of "is invalid" and
>>explain what a developper must do when he's faced to an invalid
>>selector.
>
>Good point. An invalid selector - for example - is a selector that
>generates a parsing error, ie containing an unrecognized token or a
>token which is not allowed at the current parsing point. We can
>generalize that explanation.
Thanks, I'm looking forward the next version of the Working draft of
CSS3 Selector with a clear explanation of invalid and a kind of
guidelines for developpers. :)
Thanks
--
Karl Dubost / W3C - Conformance Manager
http://www.w3.org/QA/
--- Be Strict To Be Cool! ---
Received on Monday, 12 February 2001 13:41:34 UTC