Re: [whatwg/url] Preserve "localhost" in file URLs? (#618)

@alwinb 

As for why this is the way it is, my guess is that, since it only affects Windows users, and both Chrome and Edge support `file://localhost/SomeShare`, it just hasn't been much of an issue. It may be more of an abstract concern that this standard can't express file URLs to local UNC paths.

Since I'm not a Windows user, I can't judge the impact of not fixing this. My naive assumption is that UNC is mostly used by businesses, who will likely also use the default browser (Edge), so it may become an issue when Chromium aligns with this part of the standard.

I don't know if the browsers have a way to gather telemetry on how often this comes up, but I think that would be a good idea for Chrome/Edge since this would cause a loss in functionality. @TimothyGu?

-- 
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/618#issuecomment-950947968