W3C home > Mailing lists > Public > www-validator-css@w3.org > February 2010

RE: Possible bug in CSS Validator

From: Douglas Perreault CPA* CITP <doug@perreault.us>
Date: Fri, 19 Feb 2010 14:47:15 -0500
To: <www-validator-css@w3.org>
Message-ID: <01d901cab19c$56e6a0d0$04b3e270$@perreault.us>
According to the RFC's (including 3986), it would appear to me that the
semicolon in that instance (a VMX filename terminating in a semicolon) would
have to be percent encoded for the URL to be valid if it referenced such a
file. Note that RFC 3986 discusses URIs in general whereas the CSS uses URLs
in particular. I still believe the URN portion of a URL cannot contain a
non-encoded semicolon and so the URL reference in the style sheet simply
cannot end in a semicolon.

But if I'm wrong... 

My question, and the point of my e-mail, remains -- have you ever actually
seen the use of a semicolon at the end of a URL in a CSS style sheet where
it was done on purpose? I would bet not, or if so, maybe once or twice out
of the hundreds of millions of style sheets out there. So would there really
be any harm in putting in such a warning? It would save us hours of effort
trying to figure out why a background image isn't showing. There are
warnings for much less difficult to find issues. It would seem adding a
warning for this would be the right thing to do.

--Doug

Douglas Perreault CPA* CITP
*CPA designation regulated by the State of Florida
Received on Friday, 19 February 2010 19:47:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 00:14:25 GMT