Re: [whatwg/url] Proposal: file: URL separator deduplication (#552)

To be fair, It is a bit different, as #232 collapsed a leading sequence of slashes only, somewhat mimicking the ignoring of multiple slashes before the host in other special URLs. This seems to call for collapsing all slashes in the path. 

There also were interactions with the host that made tings rather complex, especially to find a good trade-off between matching the different browser behaviours. 

We recently considered in #606 to add a percent-encoding-equivalence / normalisation to the URL equivalence section. The same could be done for file-path normalisation. Then the parser (ao.) would not become more complex.

Whether such a thing should be applied by default, is question that I don't feel qualified to answer though. Browsers in any case, don't do this. 

@karwa has done a lot of research on file paths, posted in #621 (note #618 as well). I think this would be part of that project. It's some amount of work though!



-- 
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/552#issuecomment-938637229