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

Re: Vendor-specific extensions: warnings, not errors

From: Jens O. Meiert <jens@meiert.com>
Date: Wed, 30 Jun 2010 22:19:48 -0700
Message-ID: <AANLkTikV634Q09wd5HxMAkzOFAVO6YPYiB-Gg7ViFlr0@mail.gmail.com>
To: David Dorward <david@dorward.me.uk>
Cc: www-validator-css@w3.org
A quick follow-up,

> > Of course, the validator could just accept any property starting with a dash as "OK",
> > but then people would be complaining that it was blessing -moz-bowder-radius
> > and -opacity: o.
>
> That would solve the maintenance problem on the validator team end
> though, right?
>
> Why wouldn’t a warning, clearly stating that “vendor-specific
> extensions got found and have only been checked for syntactic
> correctness”, mean a viable alternative? From my perspective it does,
> and means a win for everyone involved.

would that mean an acceptable compromise to the validator team too?

-- 
Jens O. Meiert
http://meiert.com/en/
Received on Thursday, 1 July 2010 05:20:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 00:14:26 GMT