W3C home > Mailing lists > Public > www-validator-css@w3.org > June 2005

Re: Bug with browser specific settings

From: Kravvitz <Kravvitz@DynamicSiteSolutions.com>
Date: Thu, 02 Jun 2005 14:33:16 -0400
Message-ID: <429F50EC.1050508@DynamicSiteSolutions.com>
To: www-validator-css@w3.org
CC: Sebastian Mares <sebastianmares@web.de>

Currently, CSS2.1 is only a W3C Candidate Recommendation. Its status has 
not yet been changed to full Recommendation.

The CSS Validator validates according to CSS2, not CSS2.1.

I too find it annoying. It would be nice to know why the powers that be 
are dragging their feet.

Sebastian Mares wrote:

> Well, according to section "4.1.2 Keywords" of the CSS 2.1 
> Specification, vendor-specific extensions are perfectly legal.
> "In CSS2.1, identifiers may begin with '-' (dash) or '_' (underscore). 
> Keywords and property names, beginning with -' or '_' are reserved for 
> vendor-specific extensions."
> Therefore, although they should be avoided, browser specific 
> attributes are allowed and should not be marked as illegal. Moreover, 
> even if they are illegal, this should apply to the respective rule and 
> should not affect the following attributes.
Received on Thursday, 2 June 2005 18:34:07 UTC

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