[wpt-sync] Sync PR 49725 - Avoid reliance on async module timing in import-map test
Categories
(Core :: JavaScript Engine, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 49725 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/49725
Details from upstream follow.
Yoav Weiss <yoav.weiss@shopify.com> wrote:
Avoid reliance on async module timing in import-map test
While implementing https://github.com/WebKit/WebKit/pull/37896 in WebKit, I realized that async inline module scripts run at different times there compared to Chromium.
Looking at the spec, the timing for them doesn't seem well defined, and in any case is not the subject of the test in question.
This PR modifies the test to avoid that reliance. It might be worthwhile to consider further testing for async inline module timings if interop on that front is desired, but that seems orthogonal.
|
Assignee | |
Updated•2 months ago
|
|
|
Assignee | |
Comment 1•2 months ago
|
||
|
|
Assignee | |
Comment 2•2 months ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 1 subtests
Status Summary
Firefox
OK : 1
FAIL: 1
Chrome
OK : 1
PASS: 1
Safari
OK : 1
FAIL: 1
Links
Details
New Tests That Don't Pass
- /import-maps/multiple-import-maps/resolution-consistency-in-module-tree.html [wpt.fyi]
- Module tree that started to download before a new import map should still take it into account:
FAIL(Chrome:PASS, Safari:FAIL)
- Module tree that started to download before a new import map should still take it into account:
|
||
Comment 4•2 months ago
|
||
| bugherder | ||
Description
•