1826592 - New wpt failures in /html/semantics/scripting-1/the-script-element/execution-timing/non-external-no-import.tentative.html

Status: NEW

(Core :: DOM: Core & HTML, defect)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Syncing wpt PR 39205 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

• /html/semantics/scripting-1/the-script-element/execution-timing/non-external-no-import.tentative.html [wpt.fyi]
  • Module scripts with no imports always execute asynchronously: FAIL

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1824553 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.

Comment 1

[Jon Coppeard (:jonco)]

Context from https://github.com/web-platform-tests/wpt/commit/f2151fce99621bd8e5526747f3a15d0df9741a38

Both Chrome and Safari agree that module scripts with no imports run
asynchronously, per the semi-ambiguous language in the HTML Standard
discussed in whatwg/html#3746, despite the
script being "ready" immediately. Firefox seems to implement the spec
correctly, regarding the "readiness" being synchronous, however with
2/3 implementations *not* implementing the spec in this regard, and an
open spec issue in this area, I find it unlikely that Chromium's
will change its behavior (for compat). I'll recommend on the spec issue
that we change the spec to match Safari and Chrome, and land this test
asserting the majority behavior.