Re: [whatwg/url] Review slashes after file:/// and file path normalization (#405)

Reading through the above in a bit more detail, it looks like you were asking for feedback on what approach would be most reasonable. I'll check with coworkers to see if they have any stronger opinions, but for my part, my requirements are very minimal. This is a crusty legacy area and just getting to interop is the important thing. So:

1. (Must have) Idempotency: i.e., parsing-serializing-parsing should produce the same result.

1. (Must have) Platform-independence: no differing behavior on Windows/Linux/Mac.

1. (Important) Match the maximum number of modern browser engines in the maximum number of cases as possible.

1. (Nice to have) Make the algorithm relatively simple.

1. (Nice to have) Make the mental model relatively simple. E.g. if we could explain to developers something like "localhost always goes away in this particular fashion" or "N slashes will always collapse to 4 slashes" or "slashes will never collapse" or "file URLs are just like non-file URLs in most ways" then that'd be nice.

1. (Nice to have) also try to solve related issues like #302 and #271 in ways that are satisfactory to the folks opening them.

1. (Nice to have) match legacy IE/Edge versions, since those often reflect "what enterprises expect".

Trading (3) off against the nice to haves is also reasonable. E.g. if there's a much simpler version of the algorithm that only matches 1/3 modern browser engines, then we should probably go with that. (But if it matches 0 engines, then it's not good.)

-- 
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/405#issuecomment-693554735