Re: [whatwg/url] Fix Windows drive letter handling in the file slash state (#343)

I tested by hand (https://quuz.org/url/liveview2.html) the Chrome 63.0.3213.3 for Windows - it passes all four tests and Safari 10.1.2 - also passes the tests.

Other browser's results from https://travis-ci.org/w3c/web-platform-tests/builds/274332313

_INFO: /home/travis/build/w3c/web-platform-tests/tools/ci/check_stability_

**Firefox Nightly:**

Subtest | Results | Messages
-|-|-
`Parsing: </c:/foo/bar> against <file:///c:/baz/qux>` | PASS |
`Parsing: </c\|/foo/bar> against <file:///c:/baz/qux>` | PASS |
`Parsing: <file:\c:\foo\bar> against <file:///c:/baz/qux>` | PASS |
`Parsing: </c:/foo/bar> against <file://host/path>`| PASS |

**Chrome Unstable** (google-chrome-unstable_current_amd64.deb)

Subtest | Results | Messages
-|-|-
`Parsing: </c:/foo/bar> against <file:///c:/baz/qux>`| PASS |
`Parsing: </c\|/foo/bar> against <file:///c:/baz/qux>` | FAIL | `assert_equals: href expected "file:///c:/foo/bar" but got "file:///c%7C/foo/bar"`
`Parsing: <file:\c:\foo\bar> against <file:///c:/baz/qux>` | PASS
`Parsing: </c:/foo/bar> against <file://host/path>` | FAIL | `assert_equals: href expected "file:///c:/foo/bar" but got "file://host/c:/foo/bar"`

**Microsoft Edge 14.14393**:

Subtest | Results | Messages
-|-|-
`Parsing: </c:/foo/bar> against <file:///c:/baz/qux>` | FAIL | `assert_equals: href expected "file:///c:/foo/bar" but got "file:///c:/c:/foo/bar"`
`Parsing: </c\|/foo/bar> against <file:///c:/baz/qux>` | FAIL | `assert_equals: href expected "file:///c:/foo/bar" but got "file:///c:/c%7C/foo/bar"`
`Parsing: <file:\c:\foo\bar> against <file:///c:/baz/qux>` | FAIL | `assert_equals: href expected "file:///c:/foo/bar" but got "file:///c:/c:/foo/bar"`
`Parsing: </c:/foo/bar> against <file://host/path>` | FAIL | `assert_equals: href expected "file:///c:/foo/bar" but got "file://host/c:/foo/bar"`

-- 
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/pull/343#issuecomment-329115026