Re: Vendor-specific extensions: warnings, not errors

(+Cyrille Moureaux)

Thomas, everyone interested in the subject,

> > > 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?
>
> That said, several people in the W3C team agree with your position and
> if you come up with a patch we'll be happy to review it

great news: thanks to Cyrille we do have a patch for the CSS validator
available that would throw a warning (“Property foo is an unknown
vendor extension”) instead of an error when encountering
vendor-specific extensions.

What is the suggested/preferred process now to test and include this
in the live version of the CSS validator? (The W3C might just contact
Cyrille and me—j9t at google dot com—directly to coordinate.)


Thank you,
 Jens.

-- 
Jens O. Meiert
http://meiert.com/en/