Closed Bug 1665325 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 25563 - Modernize WPT: resource-timing and navigation-timing.https.html

Categories

(Core :: DOM: Service Workers, task, P4)

task

Tracking

()

RESOLVED FIXED
83 Branch
Tracking Status
firefox83 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

b'Makoto Shimazu <shimazu@chromium.org>' wrote:

Modernize WPT: resource-timing and navigation-timing.https.html

As a part of the effort to understand the current behavior of the
resource timing, I changed the tests to use async/await for readability
with adding a few comments.

Bug: 1128786
Change-Id: I45daee67e52a13c98ad3f2010131d858a58781d3
Reviewed-on: https://chromium-review.googlesource.com/2413927
WPT-Export-Revision: 714395d023b3d956d5b5e52f23e0e2d6deb34ad5

Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core

CI Results

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

Total 2 tests and 2 subtests

Status Summary

Firefox

OK : 2
PASS: 3
FAIL: 2

Chrome

OK : 2
PASS: 5

Safari

OK : 2
PASS: 1
FAIL: 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/service-workers/service-worker/navigation-timing.https.html
Service worker controlled navigation timing: FAIL (Chrome: PASS, Safari: FAIL)
/service-workers/service-worker/resource-timing.sub.https.html
Controlled resource loads: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5d121fda693d [wpt PR 25563] - Modernize WPT: resource-timing and navigation-timing.https.html, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in before you can comment on or make changes to this bug.