Enable URLPattern tests in ShadowRealm

[ptomato]

Requires using fetch_json to download the test data.

See whatwg/urlpattern#236 for spec decision.

[wpt-pr-bot]

There are no reviewers for this pull request. Please reach out on the chat room to get help with this. Thank you!

[jeremyroman]

Have you checked to see if these tests pass today (in any engines which implement this today, which might still be Chromium)? Can you file implementation bugs against any browser where they don't pass?

When I try patching this in, I get this failure inside the WPT manifest code:

AssertionError: duplicate URL 'urlpattern/urlpattern-compare.tentative.https.any.shadowrealm-in-audioworklet.html

Possibly shadowrealm causes the non-https one to also generate such a file, and therefore it should only be listed in the .https one? (I'm not very familiar with how the WPT shadowrealm environment is generated.)

[jeremyroman]

Why do most of these specify shadowrealm but this one specifies this list instead? What is the difference?

[sisidovski]

So these are the subset of shadowrealm? Maybe it's better to set shadowrealm.

wpt/tools/manifest/sourcefile.py

Lines 100 to 106 in 2b8ebc2

	"shadowrealm": {"longhand": {
	"shadowrealm-in-window",
	"shadowrealm-in-shadowrealm",
	"shadowrealm-in-dedicatedworker",
	"shadowrealm-in-sharedworker",
	"shadowrealm-in-serviceworker",
	"shadowrealm-in-audioworklet",

[ptomato]

I left out shadowrealm-in-serviceworker and shadowrealm-in-audioworklet because service workers and audio worklets can only be created in an HTTPS context, so they'd be generated with .https. anyway, and then be duplicates of the ones generated from shadowrealm.https.any.js.

[ptomato]

Have you checked to see if these tests pass today (in any engines which implement this today, which might still be Chromium)?

Unfortunately, the intersection of engines which implement URLPattern and engines which implement ShadowRealm currently seems to be nil 😄 I'll tag @lukewarlow in here who was working on an experimental Chromium implementation of ShadowRealm at one point, to see if it had progressed far enough to check whether these tests pass.

Can you file implementation bugs against any browser where they don't pass?

Sure, will do as part of the checklist in whatwg/urlpattern#236.

When I try patching this in, I get this failure inside the WPT manifest code:

AssertionError: duplicate URL 'urlpattern/urlpattern-compare.tentative.https.any.shadowrealm-in-audioworklet.html

Possibly shadowrealm causes the non-https one to also generate such a file, and therefore it should only be listed in the .https one? (I'm not very familiar with how the WPT shadowrealm environment is generated.)

I think I missed that the urlpattern-compare test also comes in https and non-https flavours. We'll need to omit the https-only shadowrealm scopes in the non-https test, as I did with urlpattern.any.js. I'll update this PR to do that.

[lukewarlow]

URLPattern should be exposed in chrome if you enable the right flag. But chrome doesn't support importValue or dynamic imports in shadow realms so can't run WPTs unfortunately.

It also doesn't yet support shadow realm (or other Exposed=* APIs) in worklets