Re: [whatwg/url] Use different percent-encode sets for simple/non-simple scheme fragment encoding (#597)

Regarding the original issue of https://bugs.webkit.org/show_bug.cgi?id=225340, it doesn't look like a web compat issue to me. The author seemed to want to report a "deviation from the previous version of Safari" in their own application, rather than some established website that stopped working due to that change

On the other hand, the notion that some URLs canonicalized by Firefox and Chrome don't even parse with an established piece of software (Ruby) is alarming.

Given all this, I'm a fan of keeping the spec the way it is and try to get implementations to change. But failing to align all three browsers, I think Chrome should at least start escaping spaces. There is no indication that the current Chrome behavior around non-special fragments is intentional: it was introduced in https://codereview.chromium.org/23835019 / https://crbug.com/291747, which first started separating out fragments for non-special URLs.

-- 
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/597#issuecomment-832521170