I see it, but I definitely don't know what to do about it yet. As it stands, any content property's string value is always going to get url-encoded. But also as noted: rendering of the content is unaffected.
By my estimation... any quoted string value in any of the css properties that CAN contain urls is always going to get url-encoded.
|