Re: [whatwg/url] Consider always escaping U+0020 (#125)

Okay, so per the URL standard we use the "simple encode set" (which doesn't include U+0020) for hosts (doesn't matter since hosts forbid spaces anyway), cannot-be-a-base-URL paths, and fragments.

For both cannot-be-a-base-URL paths and fragments the results are identical: Chrome, Edge, and Safari do not encode U+0020, Firefox does (although Firefox does not for data URLs). I tested various schemes, including https, test, data, and x.

Given this I wonder if @zcorpan has made any progress convincing a non-Firefox browser that this is a problem. Otherwise I think we should consider this a lost cause.

-- 
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#issuecomment-278649725