Re: Vendor-specific extensions: warnings, not errors

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 UTC