Re: [whatwg/url] File URL reparse bug with percent encoded windows drive letter (#559)

Does your table include Chrome on Linux or Chrome on Windows?  There are some functional differences in Chromium's interpretation of Windows drive letters in URLs on different operating systems, as seen by looking for `C|/foo/bar` on https://wpt.fyi/results/url/url-constructor.html .  I think it's important when considering Windows drive letters what happens on Windows.  What is the behavior of new and old Edge?  What about IE?

While I do think URL parsing should be idempotent, I don't have a strong opinion here.  I initially think all those URLs should be canonicalized to `file:///c:/` and parse successfully.

-- 
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/559#issuecomment-717553034