Honestly speaking guys, I don't see the point with using the W3C CSS Validator today. If you need parsing check, it's already performed by most browsers. If you need version checking, simply stick to each style definition explained in the specs. For example, simply add &profile=cssn to your validator URI to check if your styles conform to the n spec (1, 2, 3). Of course, this is NOT mandatory, because the bigon age of W3C CSS badges is over. A website should be more than simply validated to satisfy user needs: it should be usable, user- friendly and accessible. Further, it should present interesting and useful contents. That's all. A user don't care a fig if you're using 'border-radius' or '-moz-border-radius', remember that. By the way, as a W3C translator I also noticed that most W3C pages don't validate. So what? bye ;-)
http://www.css-zibaldone.com http://www.css-zibaldone.com/test/ (English) http://www.css-zibaldone.com/articles/ (English) http://onwebdev.blogspot.com/ (English) ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
