Re: [whatwg/url] Base URL Windows drive sometimes favoured over input string drive (#574)

I would like to solve this issue. It seems to be somewhat problematic, but I can give it a try. I think it should be among the last file URL/ drive letter issues. 

My approach would be to add some cases to wpt, as a draft/ proposal at first, then collect the results and investigate how to make changes to jsdom/whatwg-url and the standard based on that. 

I propose to change the desired behaviour for cases 1. and 4. of the original issue (see below). 

**Case 1**

`file:///abc/def/../../C|/../hello/`

```
Spec:       file:///C:/hello/
Safari:     file:///C|/hello/
Firefox:    file:///hello/
Chrome/Mac: file:///hello/
Proposal:   file:///hello/
```

**Case 4**

`file:///./D|/../foo` against `file:///C:/base1/base2/`

```
Safari:     file:///D|/foo
Firefox:    file:///foo
Chrome/Mac: file:///foo
Spec:       file:///D:/foo
Proposal:   file:///foo
```
I don't have access to a Windows machine unfortunately. 

The spec would remain unchanged for the second and third cases:

* `file:/D|/../foo` against `file:///C:/base1/base2/` resolves to `file:///D:/foo`
* `file:/./D|/../foo` against `file:///C:/base1/base2/` resolves to `file:///C:/foo`

The fifth case and the one I added can maybe be kept separate, but I'm not sure yet. 

Let me know if this is OK, then I'll prepare another PR (and somehow mark it as a draft?) to the web platform tests. 

-- 
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/574#issuecomment-817821436