Closed Bug 1735723 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 31229 - Test interactions of Fetch, ResourceTiming and ServiceWorkers

Categories

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

Product:
Core
Component:
DOM: Service Workers
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
95 Branch
Tracking Flags:
Tracking Status
firefox95 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Noam Rosenthal <noam@webkit.org> wrote:

Test interactions of Fetch, ResourceTiming and ServiceWorkers

  • Worker induced delays should be reflected in ResourceTiming entry
  • Redirects & connection info should not be forwarded to the client
  • Worker-induced delays should occur before responseStart
  • requestStart should occur after fetchStart

Addresses https://github.com/whatwg/fetch/issues/1208
See https://github.com/web-platform-tests/wpt/issues/28658

Component: web-platform-tests → DOM: Service Workers
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 5 subtests

Status Summary

Firefox

OK : 1
PASS: 2
FAIL: 3

Chrome

OK : 1
PASS: 4
FAIL: 1

Safari

OK : 1
PASS: 2
FAIL: 3

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

/service-workers/service-worker/resource-timing-fetch-variants.https.html
Redirects done from within a service-worker should not be exposed to client ResourceTiming: FAIL

New Tests That Don't Pass

/service-workers/service-worker/resource-timing-fetch-variants.https.html
Redirects done from within a service-worker should not be exposed to client ResourceTiming: FAIL (Chrome: PASS, Safari: PASS)
Delay from within service-worker (after internal fetching) should be accessible through responseStart: FAIL (Chrome: PASS, Safari: FAIL)
Delay from within service-worker (before internal fetching) should be measured before responseStart in the client ResourceTiming entry: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dd27a26b614d
[wpt PR 31229] - Test interactions of Fetch, ResourceTiming and ServiceWorkers, a=testonly
https://hg.mozilla.org/integration/autoland/rev/7cc2b77e7905
[wpt PR 31229] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/dd27a26b614d
https://hg.mozilla.org/mozilla-central/rev/7cc2b77e7905

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