URL Standard – new URL()

[annevk]

Description

Let's make 2023 the year all browsers agree on a fundamental piece of the web: URLs as defined in the URL Standard.

Rationale

URLs are extremely widely used and as such would benefit from being fully interoperable.

Developers have also complained that new URL() doesn't work the same across browsers and doesn't always give the expected results for non-special schemes (e.g., non-WebKit browsers tend to stuff everything in the path).

Specification

https://url.spec.whatwg.org

Tests

https://wpt.fyi/results/url

[annevk]

(I would be okay with excluding some of the tests, such as those related to ShadowRealm.)

[tbondwilkinson]

URL compat is a P2 for Google's closure library.

"Could turn down goog.url and possibly help further migration off of goog.uri."

[foolip]

In the MDN short survey on APIs & JavaScript, "URL (parsing and API)" was selected by ~21% of survey takers, putting it in the top third of options. (There is some uncertainty as with any survey data.)

[gsnedders]

From #253:

[@foolip] URLs - using variants to web-platform-tests/wpt#37372 out the tests (file:, mailto: and javascript:) that were deemed to be too risky.

[nairnandu]

Thank you for proposing URL standard for inclusion in Interop 2023.

We are pleased to let you know that this proposal was accepted as the URL focus area. You can follow the progress of this Focus Area on the Interop 2023 dashboard.

For an overview of our process, see the proposal selection summary. Thank you for contributing to Interop 2023!

Posted on behalf of the Interop team.