This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 558 [details] SOAP output for this error. When validating CSS what includes URLs with ampersands in them, the responses do not return valid XML (or XHTML). This is because the ampersands are carried through to the output without being encoded. Example Input (typed into the TextArea or set as text in POST): .google { background-image: url(http://www.google.com/logo.jpg?is=evil&but=we_love_them_anyway); } Location of Error in SOAP output: /env:Envelope/env:Body/m:cssvalidationresponse/m:result/m:css/m:noAtRule/m:selector/m:RuleList/m:Rule/m:PropertyValue If XML encoding is too much trouble, you might consider adding CDATA blocks around the contents of this field.
This bug also happens with ">" characters in selectors, although my XML parser handles this so I am not sure if this is as severe as the above bug. Input: .google > .yahoo { color: red; } Some of the problem Areas: /env:Envelope/env:Body/m:cssvalidationresponse/m:result/m:warnings/m:warninglist/m:warning/m:context /env:Envelope/env:Body/m:cssvalidationresponse/m:result/m:css/m:noAtRule/m:selector/m:selectorValue
Created attachment 559 [details] Output from using a ">" in a selector
Created attachment 619 [details] test case as standalone css file
Fixed by adding new function to generate escaped versions. the XHTML and SOAP1.2 templates are now using those functions. See http://qa-dev.w3.org:8001/css-validator/