W3C home > Mailing lists > Public > www-validator-css@w3.org > January 2011

Re: Vendor-specific extensions: warnings, not errors

From: Yves Lafon <ylafon@w3.org>
Date: Sat, 15 Jan 2011 15:51:07 -0500 (EST)
To: "Jens O. Meiert" <jens@meiert.com>
cc: Thomas Gambet <tgambet@w3.org>, www-validator-css@w3.org, Cyrille Moureaux <cyrille@google.com>
Message-ID: <alpine.DEB.1.10.1101151549530.15930@wnl.j3.bet>
On Fri, 31 Dec 2010, Jens O. Meiert wrote:

As a followup to the mailing list...

Cyrille sent us a patch that was integrated. The result is available on 
the dev validator at http://qa-dev.w3.org:8001/css-validator/

Thanks again Cyrille and Jens !

> (+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.

Baroula que barouleras, au tiƩu toujou t'entourneras.

Received on Saturday, 15 January 2011 20:51:09 UTC

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