Re: [whatwg/url] Should we unescape characters in path? (#606)

> I think it's okay to say that for path/query/fragment we generally expect https://url.spec.whatwg.org/#string-percent-decode to work

A good way to go about that is to point out in the standard that there are multiple normalisations/ equivalence relations on URLs that are in common use, and add a section, maybe? to explain that. I suppose, in the WHATWG style it would contain algorithms that compute them. (With a statement that they are not normative for browsers, where this is the case). 

Percent encoding normalisation / equivalence is a good one to start with. 

Collapsing slashes could be another one to mention. IIRC this is relevant also to another open issue about JS module specifiers. 



-- 
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/606#issuecomment-930103703