CSS Validation Will Soon Be More Realistic
Jens O. Meiert, January 25, 2011 (↻ August 16, 2013).
This entry’s been written by Jens the Web Developer.
A brief update on making use of vendor-specific CSS extensions warnings, not errors: the development version of the CSS validator contains an update that doesn’t penalize for use of such extensions. (To try the update customize the “Options” by setting “Vendor Extensions” to “Warnings”.)
Why does this matter again? Web developers shouldn’t be dinged for syntactically correct use of CSS that proves to be necessary in practice, especially if it does not impose any maintenance issues and allows authors to easily adjust course. This is my very own take however it matches observations we made at Google when we, some time ago, introduced more comprehensive web page quality checks and guidelines that go far beyond validation. (I briefly touched quality at Google before and might talk about the subject again.)
We estimate to update the live validator around the beginning of February.
My involvement was more of “stimulus” nature: special thanks to Cyrille Moureaux (Google) who provided the actual validator patch as well as Thomas Gambet and Yves Lafon (W3C) who included the patch in the validator code base.
Update (January 31, 2011)
Enjoy the most popular posts, perhaps including:
Leave a Comment
Unfortunately, comments are closed.