This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
h1 { border-right: "foo" bar 10 } is invalid, but the validator does not complain about it if a specific medium (a non-null medium) is specified, see e.g. http://jigsaw.w3.org/css-validator/validator?text=h1+%7B+border-right%3A+%22foo% 22+bar+10+%7D&warning=2&profile=css2&usermedium=all http://jigsaw.w3.org/css-validator/validator?text=h1+%7B+border-right%3A+%22foo% 22+bar+10+%7D&warning=2&profile=css2 for a demonstration. It's likely that this is not limited to border-right. See http://www.w3.org/mid/3f450278.182632651@smtp.bjoern.hoehrmann.de
Created attachment 376 [details] Junk values in shorthand declarations
The phenomenon of accepting junk values in shorthand declarations and generating valid values in the internal model is spread across the properties 'background', 'border-bottom', 'border-left', 'border-right', 'border-top', and 'list-style'. All of these properties require at least one term, permit more than one term, use white space as a term separator, and do not require any particular ordering of the terms that appear. The "Value" fields of the definitions of these properties use as their only conjoiner the double vertical line ("||"). For reasons unknown to me, invalid 'border' declarations raise an error rather than participating in the phenomenon described
Fixed, see http://qa-dev.w3.org:8001/css-validator/