- From: Simon Pieters <notifications@github.com>
- Date: Fri, 27 May 2016 05:59:39 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc:
Received on Friday, 27 May 2016 13:00:06 UTC
In https://github.com/whatwg/url/commit/ad3660f97132738b6b2ff0020656e4cb87365f00 U+0020 changed from being escaped to be not escaped for schemes like data javascript mailto etc. Rationale seems to be that it's what some browsers did back then, per http://krijnhoetmer.nl/irc-logs/whatwg/20121026#l-573 Test http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4238 It appears that Gecko still escapes space in all of these cases. Are there known Web-compat problems for Gecko because of this? Round-tripping the space can be problematic because space is like the only character that really separates a URL from the next or from the following text. Features like `ping=""` and `srcset=""` will get bogus values if someone assumes that a parse-serialization roundtrip will eliminate spaces from a URL (and it *typically* does). --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/125
Received on Friday, 27 May 2016 13:00:06 UTC