Closed Bug 1921927 Opened 2 months ago Closed 1 month ago

[wpt-sync] Sync PR 48398 - Update SW static routing API resource timing with worker prefix

Categories

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

task

Tracking

()

RESOLVED FIXED
133 Branch
Tracking Status
firefox133 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Keita Suzuki <suzukikeita@chromium.org> wrote:

Update SW static routing API resource timing with worker prefix

This CL updates ServiceWorker static routing API resource timing
information to add the worker prefix to the fields.

Explainer: https://github.com/WICG/service-worker-static-routing-api/blob/main/resource-timing-api.md
Bug: 41496865
Change-Id: I6f96b5aca0fdd389a04eb32bb77c39f010078109
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5898207
Reviewed-by: Shunya Shishido \<sisidovski@chromium.org>
Reviewed-by: Takashi Toyoshima \<toyoshim@chromium.org>
Reviewed-by: Yoshisato Yanagisawa \<yyanagisawa@chromium.org>
Commit-Queue: Keita Suzuki \<suzukikeita@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1362186}

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

CI Results

Ran 9 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
FAIL: 14

Chrome

OK : 1
FAIL: 14

Safari

OK : 1
FAIL: 14

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /service-workers/service-worker/tentative/static-router/static-router-resource-timing.https.html [wpt.fyi]
    • Main resource matched the rule with fetch-event source: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load matched with the condition and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load not matched with the condition and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load matched with the cache source and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource fallback to the network when there is no cache entry and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched the rule fetch-event source: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load not matched with URLPattern condition: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched with URLPattern condition: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched with the cache source rule: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load did not match with the cache and fallback to the network: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load matched the rule with race-network-and-fetch-handler source, and the fetch handler response is faster than the server response: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load matched the rule with race-network-and-fetch-handler source, and the server reseponse is faster than the fetch handler: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched the rule with race-network-and-fetch-handler source, and the fetch handler response is faster than the server response: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched the rule with race-network-and-fetch-handler source, and the server reseponse is faster than the fetch handler: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2e543775fc82 [wpt PR 48398] - Update SW static routing API resource timing with worker prefix, a=testonly
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
You need to log in before you can comment on or make changes to this bug.