W3C home > Mailing lists > Public > www-validator-css@w3.org > July 2009

Re: Ability to filter part of the CSS validation

From: James Hopkins <james@idreamincode.co.uk>
Date: Thu, 9 Jul 2009 10:55:14 +0100
Message-Id: <DBA30164-6B80-4ADD-93CD-706873166653@idreamincode.co.uk>
To: Yann Esposito <yann.esposito@gmail.com>
Cc: "www-validator-css@w3.org" <www-validator-css@w3.org>
> I saw in your FAQ that you cannot validate CSS with -moz-*  
> properties for example.
> But most of time, these properties are used just to give a better  
> user experience for those who user latest web browser.

This isn't the case. Vendor prefixes have several different purposes  
including, highlighting partial inplementations of W3C specs, as well  
as being used when vendors decide to include proprietary or  
experimental  feature inplementations.

> Why not include a way to tell the validator to filter all these  
> properies?

Some time ago in this list, there was a call for suggestions as to  
what features the new validator should include. I for one suggested  
that the new validator should recognise each prefix and inform the  
user that they are using a property that will be recognised only by a  
specific browser.

I suggest that this method is a better solution than for the validator  
to just ignore properties prepended with these extensions.

> For example, including a comment:
> /* Do not Validate BEGIN */
>  -moz-....
>  -webkit-...
> /* Do not Validate END */
> or in the url which tell the validator to ignore all properies  
> begining by '-' such as -moz*, -webkit*...
> http://jigsaw.w3.org/css-validator/check/referer?profile=css3&ignoreproprietary=true
> But this are just example and I believe it should not be too  
> difficult to implement.
> The advantage would be to provide a validation for CSS which use web  
> browser specific properties.
> regards,
> YE
Received on Thursday, 9 July 2009 09:55:40 UTC

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