W3C home > Mailing lists > Public > public-css-testsuite@w3.org > March 2009

RE: attribute-value-selector-004.xht not well formed

From: Robert Stam <robert@tallcomponents.com>
Date: Wed, 11 Mar 2009 13:22:38 -0500
Message-ID: <40BA97F694BF944EBB093147C3423790060D2280@34093-EVS2C2.exchange.rackspace.com>
To: <public-css-testsuite@w3.org>
Cc: "L. David Baron" <dbaron@dbaron.org>

> -----Original Message-----
> From: public-css-testsuite-request@w3.org
[mailto:public-css-testsuite-
> request@w3.org] On Behalf Of L. David Baron
> Sent: Wednesday, March 11, 2009 6:59 PM
> To: public-css-testsuite@w3.org
> Subject: Re: attribute-value-selector-004.xht not well formed
> 
> On Tuesday 2009-03-10 10:59 -0700, Arron Eicholz wrote:
> > The rule is in 5.8.1 "Attribute values must be identifiers or
> > strings."
> 

Not sure, but it looks like the test don't use an attribute value, but
an attribute name (which must be an IDENT)

> But that's not a statement about selector matching.  It's only an
> authoring conformance requirement and a statement about validity,
> and it's only turned into an implementation conformance requirement
> by the statement in 4.1.7:
> 
>   # When a user agent can't parse the selector (i.e., it is not
>   # valid CSS 2.1), it must ignore the declaration block as well.
> 
> -David
> 
> --
> L. David Baron                                 http://dbaron.org/
> Mozilla Corporation                       http://www.mozilla.com/
> 
> 
> 

Best Regards,
Robert Stam

TallComponents
Received on Wednesday, 11 March 2009 18:23:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 17:51:58 GMT