Open
Bug 1866205
Opened 1 year ago
Updated 7 months ago
New wpt failures in /html/semantics/scripting-1/the-script-element/module/top-level-await/ [sibling-imports-not-blocked.any.worker.html, sibling-imports-not-blocked.any.html]
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: wpt-sync, Unassigned)
References
Details
(Whiteboard: [wpt])
Syncing wpt PR 42944 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
- /html/semantics/scripting-1/the-script-element/module/top-level-await/sibling-imports-not-blocked.any.worker.html [wpt.fyi]
- Async modules only scheduling microtasks don't block execution of sibling modules:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Async modules only scheduling microtasks don't block execution of sibling modules:
- /html/semantics/scripting-1/the-script-element/module/top-level-await/sibling-imports-not-blocked.any.html [wpt.fyi]
- Async modules only scheduling microtasks don't block execution of sibling modules:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Async modules only scheduling microtasks don't block execution of sibling modules:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1863002 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
Updated•7 months ago
|
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•