This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24246 - Percent-encode spaces in scheme data
Summary: Percent-encode spaces in scheme data
Status: RESOLVED INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-08 23:35 UTC by Santiago M. Mola
Modified: 2015-06-15 14:50 UTC (History)
2 users (show)

See Also:

Attachments

Description Santiago M. Mola 2014-01-08 23:35:29 UTC 
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?
Comment 1 Anne 2014-01-10 11:40:43 UTC 
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...
Comment 2 Anne 2014-01-15 13:56:25 UTC 
WebKit, Blink, and Trident do not escape them.

Can you explain how it would be safer to escape them?
Comment 3 Michael[tm] Smith 2014-03-13 07:14:24 UTC 
FYI https://github.com/w3c/web-platform-tests/pull/767
Comment 4 Santiago M. Mola 2014-03-13 19:34:42 UTC 
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.
Comment 5 Sam Ruby 2014-12-05 00:38:08 UTC 
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).
Comment 6 Anne 2015-06-15 14:50:14 UTC 
The test seems fine. IE should simply be fixed.