This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
User's manual states that, by default, the W3C online validator will check for compliance against CSS2, the current recommendation. However, it appears that the validator is actually parsing documents using CSS2.1 rules. I was getting unexplainable errors when validating my style sheet, which uses the @font-face at-rule. After digging deep into the specification and a lot of head banging, I finally figured out the problem once I realized I could tell the validator what specification to use. My style sheet validates against CSS2, but it looks like the @font-face at-rule has been removed in CSS2.1. This is the first time I had ever made use of this rule and ended up wasting a ton of time chasing ghosts.
The bug is rather in the manual which should be updated. We used CSS 2.1 as default at this point.
Why would you use CSS 2.1 as the default at this point? At this point 2.0 is the current recommendation?
(In reply to comment #2) > Why would you use CSS 2.1 as the default at this point? At this point 2.0 is > the current recommendation? CSS 2.1 is generally considered as an errata to CSS2, and in particular, is closer to actual implementations than CSS 2.
Actually, the CSS validator should be checking against all CR+ level CSS specs by default.
The documentation bug still exists, over 5 years after it was reported here, and now it is a double bug: http://jigsaw.w3.org/css-validator/manual.html says that for the profile parameter, the default value is "the most recent W3C Recommendation: CSS 2". CSS 2.1 is now the most recent recommendation (regarding CSS as a whole), whereas the default value is now CSS3, though there is no public documentation on what this means. My guess is that the intent is that here "CSS3", or "CSS Level 3" as it is called in the UI, is CSS 2.1 plus CSS 3 specifications that have CR or REC status.