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

domenic left a comment (whatwg/url#874)

We still don't have a version of the whatwg-url pull request which matches this spec, but we're getting kind of closer: https://github.com/jsdom/whatwg-url/pull/304#pullrequestreview-3420613501 .

The good news is that https://github.com/web-platform-tests/wpt/pull/53459 looks quite comprehensive: a lot of good test cases.

The trickier news is that according to the results:

- https://wpt.fyi/results/url/a-element-xhtml.xhtml%3Finclude%3Dfile?diff&filter=ADC&run_id=5179483993931776&run_id=5108083115425792
- https://wpt.fyi/results/url/a-element-xhtml.xhtml%3Finclude%3Dfile?diff&filter=ADC&run_id=5119034879377408&run_id=5173297898848256
- https://wpt.fyi/results/url/url-constructor.any.html%3Finclude%3Dfile?diff&filter=ADC&run_id=5180821809135616&run_id=5129564797009920

this spec change does not necessarily bring us in line with what browsers seem to do. Almost all of the new tests fail in all browsers. This is probably Safari and Firefox do not seem to have any special drive letter handling. Chrome has some, but only on Windows platforms, which are not what are tested in CI.

So I guess the question of multi-implementer interest is still unclear. But I suspect this is an improvement... Maybe doing a WPT run on Chrome Windows would make it clearer.

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

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