Hi,
On Thu, Jun 05, 2014 at 11:39:28PM -0700, S Page wrote:
[ Jigsaw CSS validator over-complaining ]
Full ACK.
Especially, the relevant data uris like
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAAuCAIAAABmjeQ9AAAARElEQVR42mVO2wrAUAhy/f8fz+niVMTYQ3hLKkgGgN/IPvgIhUYYV/qogdP75J01V+JwrKZr/5YPcnzN3e6t7l+2K+EFX91B1daOi7sAAAAASUVORK5CYII=
match the specification's regular expressions for unquoted url characters [1].
That said ... while standard conformance is nice here, if others have the feeling that we should quote them nonetheless, I do not see an issue with quoting them.
Besides the other theories advanced, might it be sporadic ResourceLoader mis-minification?
I had tried loading the resources several times from different servers, but that didn't bring up anything useful.
What's the HTTP Referer for these requests, can we tell if it's coming from an external <link rel > to CSS or CSS a mw.loader.implement() piece of JavaScript inserting the CSS?
The referer is empty for ~97% of affected requests.
The chain of requests looks like this:
1. Client fetches some page (like http://pt.wikipedia.org/wiki/Copa_do_Mundo_FIFA )
2. Client fetches resources for this page (like http://bits.wikimedia.org/pt.wikipedia.org/load.php?%5B...] with referer http://pt.wikipedia.org/wiki/Copa_do_Mundo_FIFA ).
3. Client fetches urls with data uri appended (like http://pt.wikipedia.org/wiki/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAA... with empty referer).
Thanks, Christian
[1] Well ... both of them. In [2] (normative) the regular expression
[!#$%&*-[]-~]
is used while [3] (also normative :-/ ) uses
[!#$%&*-~]
. So they differ in \ handling. But regardless of the choice of the above variants, the above url is matched by any of them.
[2] http://www.w3.org/TR/CSS21/syndata.html#tokenization:
[3] http://www.w3.org/TR/CSS21/grammar.html#scanner