24246 2014-01-08 23:35:29 +0000 Percent-encode spaces in scheme data 2015-06-15 14:50:14 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED INVALID P2 normal Unsorted 1 santi annevk mike rubys sideshowbarker+urlspec oldest_to_newest 98168 0 santi 2014-01-08 23:35:29 +0000 Gecko does percent-encode spaces in scheme data. Blink does not. W3C's web-platform-tests expect them to be encoded. Why does the spec doesn't percent encode them? Isn't it better to be on the safe side? 98255 1 annevk 2014-01-10 11:40:43 +0000 Is space the only difference? It seems my reference implementation is a bit different here too: https://github.com/annevk/url/blob/master/url.js It only has two escape methods... 98499 2 annevk 2014-01-15 13:56:25 +0000 WebKit, Blink, and Trident do not escape them. Can you explain how it would be safer to escape them? 102296 3 mike 2014-03-13 07:14:24 +0000 FYI https://github.com/w3c/web-platform-tests/pull/767 102313 4 santi 2014-03-13 19:34:42 +0000 I have no point for or against percent-encoding spaces here. I probably opened this issue because of the discrepancy with web-platform-tests and Gecko. 115959 5 rubys 2014-12-05 00:38:08 +0000 Given that Santiago likely opened this due to a test discrepancy, I'd suggest closing this as WONTFIX, for the reason that Anne said: WebKit, Blink, and Trident don't escape them: https://url.spec.whatwg.org/interop/urltest-results/bf8630587b Note: I'd also suggest that we either change that test or add another one, as IE treats a one character scheme as a drive letter. https://url.spec.whatwg.org/reference-implementation/liveview.html can be used to explore browser behavior (that's how I verified IE's behavior with a multi-character scheme). 120994 6 annevk 2015-06-15 14:50:14 +0000 The test seems fine. IE should simply be fixed.