Closed Bug 1768981 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 34038 - Add a WPT for when a <script> is not implicitly potentially render-blocking

Categories

(Core :: DOM: Core & HTML, task, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
102 Branch
Tracking Flags:
Tracking Status
firefox102 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 34038 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/34038
Details from upstream follow.

Xiaocheng Hu <xiaochengh@chromium.org> wrote:

Add a WPT for when a <script> is not implicitly potentially render-blocking

For https://github.com/whatwg/html/pull/7894

Bug: 1271296
Bug: https://github.com/whatwg/html/issues/7893
Change-Id: I95609738722122c96d65ccc588cbbd4c90ce67ec

Reviewed-on: https://chromium-review.googlesource.com/3643218
WPT-Export-Revision: 503c2f12f2ccaff875c0c7d65d6fe5641f9b3a2c

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 14 subtests

Status Summary

Firefox

OK : 1
PASS: 14

Chrome

OK : 1
PASS: 14

Safari

OK : 1
PASS: 14

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8f079279e15c
[wpt PR 34038] - Add a WPT for when a <script> is not implicitly potentially render-blocking, a=testonly

https://hg.mozilla.org/mozilla-central/rev/8f079279e15c

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox102: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in before you can comment on or make changes to this bug.