Re: [whatwg/url] feat: handle Windows file paths with backslashes in URL parsing (PR #874)

annevk left a comment (whatwg/url#874)

I think the simplest rule is if we treat ASCII letter, followed by `:\` as a Windows `file:` URL path. That means that the first of the invalid drive letter cases would not be considered a `file:` URL path (but instead a regular URL whose scheme is `cc`). The other two would be and hopefully parsing would just fall out of how paths are parsed?

If you only have device paths without a base URL I think those would end up failing to parse. I don't think we want to add support for those. At least that would go quite a bit beyond the original proposed scope.

For special characters in paths I would hope we can support those in the same way we support them in paths today. Is there a need for special cases?

A UNC path with a `http:` base URL I would expect to follow the existing code path for that.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/874#issuecomment-3381441186
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/pull/874/c3381441186@github.com>