Split some URL tests into separate files to allow for better ShadowRealm coverage

[ptomato]

Test List

https://wpt.fyi/results/url?sha=f382c0ce93&max-count=2&product=chrome&product=firefox&product=safari&view=interop&q=IdnaTestV2.any.html%20or%20IdnaTestV2.window.html%20or%20urlencoded-parser.any.html%20or%20urlencoded-parser.any.worker.html%20or%20urlencoded-parser-request-response.any.html%20or%20failure.html%20or%20url-constructor-base-failure.any.html

Rationale

As part of the TC39 ShadowRealm proposal we are trying to increase WPT coverage for the various Web APIs exposed in ShadowRealm. This includes running existing tests for APIs such as URL in ShadowRealm scopes. However, in order to run as many test files as possible in ShadowRealm scopes, it's necessary to split some of the files that previously contained a mix of tests both suitable and unsuitable for executing in ShadowRealm scopes. See web-platform-tests/wpt#41985 for more details.

Here are the splits and renames made in that PR that are relevant to Interop:

• urlencoded-parser.any.js → split out urlencoded-parser-request-response.any.js
• failure.html → split out url-constructor-base-failure.any.js
• IdnaTestV2.window.html → renamed to IdnaTestV2.any.html

Concretely, we propose to add the following tests to the Interop 2023 URL label:

• IdnaTestV2.any.html
• url-constructor-base-failure.any.html
• urlencoded-parser-request-response.any.html

and remove:

• IdnaTestV2.window.html

(See web-platform-tests/wpt-metadata#6930 for how this would be implemented in wpt-metadata.)

Because subtests have different weights in the Interop score depending on how many other subtests there are in the file, this has an effect on the scores, although it is small. Here is a wpt.fyi link (courtesy of @gsnedders) that I believe shows the effect on the scores. From the numbers there:

• Chrome: 95.39% → 95.55%
• Firefox: 99.28% → 99.10%
• Safari: 99.78% → 99.80%

[nairnandu]

@hayatoito could you review this change for Chromium?
@jgraham could you review this change for Gecko?
@gsnedders or @nt1m could you review this change for WebKit?

[hayatoito]

I don't disagree, but splitting URL tests into separate files requires a bunch of expectation files rebase in Chromium. It might be better to plan who will work on that before actually doing it so that we don't upset Chromium.

[ptomato]

Hopefully that wouldn't be too big in scope; maybe similar to https://github.com/web-platform-tests/wpt-metadata/pull/6930/files?

[zcorpan]

URL is no longer an active focus area in 2025, and the dashboard for this year doesn't include a table for previous focus areas. So, I think signoff from Interop is not needed anymore for this change, but coordinating here could still be useful. cc @valenting

[nairnandu]

Closing this issue as the URL focus area is not carried over into 2025