First, I KNOW that the full validators are picky and annoying and sometimes downright wrong.
That said, I tried to run a nice automated validator (W3C LogValidator) over a lightweight site in Corolla, and got a slew of complaints - not from the HTML, but from the CSS checker.
base.css 31 errors
style.css 74 errors
colors.css 8 errors
Now, don't panic as most of these are about the custom moz- or webkit- rounded corners and extensions. I thought the validator would know how to ignore them however...
Does anyone know a way of making them 'allowed' in the strict validator?
Anyway, on a working (dev) site I also got a load of warnings about foreground-background colors coming out the same. Not sure if that's actually what's happening.
I'll go looking for a legal way of adding borders that the validator won't complain about, but thought I'd note this issue for consideration at some point.
Comments
Comment #1
Jarek Foksa CreditAttribution: Jarek Foksa commentedYeah, W3C validator does not recognize many CSS3 properties, especially those defined in working drafts.
I validated current version of Corolla for Drupal 6 using the new Unicorn validator. Out of 80 errors I got for CSS3 profile, I haven't found any properties/values that would violate CSS3 specs.
I guess the best thing we can do is to wait until W3C upgrades the validator.
Comment #2
dman CreditAttribution: dman commentedYeah, it was Unicorn I was looking at. I thought there was something I'd missed about how to use new CSS extensions without triggering "error"s. "Warnings" I could live with. I thought the syntax allowed for that. Not found the right syntax yet.
Comment #3
Jarek Foksa CreditAttribution: Jarek Foksa commentedThe syntax for vendor extensions (-moz-property-name, -webkit-property-name) is even defined in
CSS2 specification. I really have no idea why validator marks them as errors instead of warnings.
Comment #4
dman CreditAttribution: dman commentedOK, We'll blame the validator for now then.