This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The check referer facility should understand the profile option. It would be very appreciated if we could set up on web pages links like http://jigsaw.w3.org/css-validator/check/referer&profile=css21 Rationale: 1. http://jigsaw.w3.org/css-validator/check/referer won't validate pages with some CSS2.1 specific properties (for example display:inline-block) but which are valid according to the CSS 2.1 spec. 2. We can already do use links like http://jigsaw.w3.org/css-validator/validator?uri=http://xxx&profile=css21 3. Using the above syntax (specifying an explicit URI) forces us to compute the page url for each web page, which can consume some precious time in some cases. Agreed that this puts the burden on the W3C machines, but those machines will only to have to do the computation when asked, not for every page rendering.
http://jigsaw.w3.org/css-validator/check?uri=referer&profile=css21 ?
http://jigsaw.w3.org/css-validator/check?uri=referer&profile=css21 works just fine and solves the problem. Thanks! Is this syntax (http://jigsaw.w3.org/css-validator/check?uri=referer) documented somewhere on the CSS validator pages? Maybe it should before this bug report is closed?
We don't really have much documentation on the CSS Validator, I don't think it's documented on the homepage, no.
The functionality is here. This is not a bug. Bug #2493 is about providing a documentation on all the possible ways to call the CSS validator.