service-workers

edit

WPT coverage of the tests of service-workers at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable257283492%
Tentative711064%
Reftests110100%
Crash tests23067%
All267298491%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • BUG: 2
  • TEST BUG: 17
  • NOT IMPLEMENTED: 7
  • TEST RUNNER: 5

Stable tests

TestResultSubtestsKindDescription
cache-storage/cache-abort.https.any.jsPass36 / 36
cache-storage/cache-add.https.any.jsFail92 / 96TEST BUG"Cache.addAll should succeed when an entry matches an earlier entry only under its own vary header": vary.py sets the Vary header from the cookie with str() of bytes (Python 3), i.e. Vary: b'x-shape', a header that neither request has: the two requests match under the Vary of the first response, so addAll() rejects with an InvalidStateError (https://w3c.github.io/ServiceWorker/#batch-cache-operations)
cache-storage/cache-api-nested-worker.https.htmlPass1 / 1
cache-storage/cache-delete.https.any.jsPass36 / 36
cache-storage/cache-keys-attributes-for-service-worker.https.htmlPass2 / 2
cache-storage/cache-keys.https.any.jsPass68 / 68
cache-storage/cache-match.https.any.jsPass100 / 100
cache-storage/cache-matchAll.https.any.jsPass64 / 64
cache-storage/cache-put.https.any.jsPass108 / 108
cache-storage/cache-storage-buckets.https.any.jsPass8 / 8
cache-storage/cache-storage-keys.https.any.jsPass4 / 4
cache-storage/cache-storage-match.https.any.jsPass44 / 44
cache-storage/cache-storage.https.any.jsPass40 / 40
cache-storage/common.https.window.jsPass1 / 1
cache-storage/credentials.https.htmlPass1 / 1
cache-storage/sandboxed-iframes.https.htmlPass2 / 2
idlharness.https.any.jsPass787 / 787
service-worker/Service-Worker-Allowed-header.https.htmlPass8 / 8
service-worker/ServiceWorkerGlobalScope/close.https.htmlPass2 / 2
service-worker/ServiceWorkerGlobalScope/error-message-event.https.htmlPass1 / 1
service-worker/ServiceWorkerGlobalScope/extendable-message-event-constructor.https.htmlPass10 / 10
service-worker/ServiceWorkerGlobalScope/extendable-message-event.https.htmlPass4 / 4
service-worker/ServiceWorkerGlobalScope/fetch-on-the-right-interface.https.any.jsPass1 / 1
service-worker/ServiceWorkerGlobalScope/isSecureContext.https.htmlPass2 / 2
service-worker/ServiceWorkerGlobalScope/message-event-ports.https.htmlPass1 / 1
service-worker/ServiceWorkerGlobalScope/postmessage.https.htmlPass2 / 2
service-worker/ServiceWorkerGlobalScope/registration-attribute.https.htmlPass2 / 2
service-worker/ServiceWorkerGlobalScope/service-worker-error-event.https.htmlPass1 / 1
service-worker/ServiceWorkerGlobalScope/unregister.https.htmlPass4 / 4
service-worker/ServiceWorkerGlobalScope/update.https.htmlPass1 / 1
service-worker/about-blank-replacement.https.htmlFail4 / 7BUGthe document that replaces the initial about:blank document of an iframe or a popup reuses its Window, but its client has the id of the reserved client of the navigation (FetchEvent.resultingClientId) instead of the id of the environment of the initial document, which the window keeps (https://html.spec.whatwg.org/multipage/document-lifecycle.html#initialise-the-document-object). Keeping the id of the initial document breaks clients.get(resultingClientId) in clients-get-resultingClientId.https.html, clients-get.https.html and navigation-redirect.https.html, whose iframes navigate away from their initial about:blank document (Chrome and Safari fail the same three subtests of this test); the other subtests pass
service-worker/activate-event-after-install-state-change.https.htmlPass1 / 1
service-worker/activation-after-registration.https.htmlPass1 / 1
service-worker/activation.https.htmlPass4 / 4
service-worker/active.https.htmlPass2 / 2
service-worker/add-routes.https.htmlPass1 / 1
service-worker/claim-affect-other-registration.https.htmlPass1 / 1
service-worker/claim-fetch.https.htmlPass1 / 1
service-worker/claim-not-using-registration.https.htmlPass2 / 2
service-worker/claim-shared-worker-fetch.https.htmlPass1 / 1
service-worker/claim-using-registration.https.htmlPass2 / 2
service-worker/claim-with-redirect.https.htmlPass1 / 1
service-worker/claim-worker-fetch.https.htmlFail3 / 6TEST BUGthe test expects clients.claim() to claim a worker created from a blob: URL; the creation URL of that worker is its blob: URL, which does not match the scope of the registration (https://w3c.github.io/ServiceWorker/#clients-claim), so the worker keeps the controller of its creator. Firefox fails the same three subtests
service-worker/client-id.https.htmlPass1 / 1
service-worker/client-navigate.https.htmlFail9 / 10TEST BUGthe Frame location should not update on failed mixed-content navigation subtest: a navigation of WindowClient.navigate() that is blocked as mixed content gets a network error, so the navigable loads an error document whose origin is opaque (https://html.spec.whatwg.org/multipage/browsing-the-web.html#populating-a-session-history-entry), and navigate() is rejected with a TypeError; the test expects the frame to keep its document, as the browsers cancel the navigation (unspecified): reading location.href of the error document throws a SecurityError. The other subtests pass
service-worker/client-url-creation-url.https.htmlTimeout0 / 10TEST BUGthe iframe posts a message to its parent while it is parsed (client-url-creation-url-iframe.html), and the test adds its message listener only after the load event of the iframe (with_iframe()): the HTML Standard queues the DOMContentLoaded and load events in tasks of the DOM manipulation task source at the end of the parsing (https://html.spec.whatwg.org/multipage/parsing.html#the-end), after the task of the message (posted message task source), and the order in which the event loop runs the tasks of different task sources is implementation-defined (https://html.spec.whatwg.org/multipage/webappapis.html#event-loop-processing-model, step 2.1): the test relies on the browsers firing the events of a small document in the task that ends its parsing, so the message is lost and every subtest times out
service-worker/client-url-of-blob-url-worker.https.htmlPass1 / 1
service-worker/clients-get-client-types.https.htmlPass1 / 1
service-worker/clients-get-cross-origin.https.htmlPass1 / 1
service-worker/clients-get-resultingClientId.https.htmlPass6 / 6
service-worker/clients-get.https.htmlPass3 / 3
service-worker/clients-matchall-blob-url-worker.https.htmlPass2 / 2
service-worker/clients-matchall-client-types.https.htmlPass2 / 2
service-worker/clients-matchall-exact-controller.https.htmlPass1 / 1
service-worker/clients-matchall-frozen.https.htmlFail0 / 1TEST BUGthe windows are opened by window.open(), so they are auxiliary browsing contexts whose frameType is auxiliary (https://w3c.github.io/ServiceWorker/#dom-client-frametype), not top-level; their lifecycleState is correct (frozen for the window frozen by test_driver.freeze())
service-worker/clients-matchall-include-uncontrolled.https.htmlPass2 / 2
service-worker/clients-matchall-on-evaluation.https.htmlPass1 / 1
service-worker/clients-matchall-order.https.htmlFail4 / 7TEST RUNNERthe three subtests of the uncontrolled windows expect the window of the WPT harness (/testharness_runner.html) among the clients; the subtests of the controlled windows pass
service-worker/clients-matchall.https.htmlPass1 / 1
service-worker/controlled-dedicatedworker-postMessage.https.htmlDisabled–TEST RUNNERthe fetch handler of the service worker answers the script of the dedicated worker after a setTimeout(1000) of the service worker: the event loop of the runner does not advance the virtual clock while the dispatch of the fetch event and the fetch of the script of the worker are running, so the clock only advances by the 100 µs of each of its reads, between the waits of the loop; it exceeded the 60 s limit on Windows (15.6 ms timer period, now 1 ms) and on a loaded macOS machine when the whole suite ran. When it completes, 2 of its 4 subtests fail: the messages that the service worker posts to the client of resultingClientId during the fetch event do not reach the worker
service-worker/controlled-iframe-postMessage.https.htmlFail3 / 5TEST BUGthe service worker calls clients.get(event.resultingClientId) while it handles the navigation, and only starts the timer that resolves its respondWith() once get() settles: the Service Workers specification waits for the client to be execution ready (https://w3c.github.io/ServiceWorker/#clients-get, step 2.1.2), i.e. for the document that the response creates, so the frame would never load (Chrome fails these subtests); the library resolves get() with undefined at once for a reserved client, and Firefox and Safari resolve it with the reserved client and queue its messages
service-worker/controller-on-disconnect.https.htmlPass1 / 1
service-worker/controller-on-load.https.htmlPass1 / 1
service-worker/controller-on-reload.https.htmlPass1 / 1
service-worker/controller-with-no-fetch-event-handler.https.htmlPass5 / 5
service-worker/credentials.https.htmlPass5 / 5
service-worker/css-sw-same-origin-substitution.https.htmlPass1 / 1
service-worker/data-iframe.htmlPass1 / 1
service-worker/data-transfer-files.https.htmlPass1 / 1
service-worker/dedicated-worker-service-worker-interception.https.htmlPass3 / 3
service-worker/detached-context.https.htmlPass4 / 4
service-worker/embed-and-object-are-not-intercepted.https.htmlPass8 / 8
service-worker/extendable-event-async-waituntil.https.htmlPass14 / 14
service-worker/extendable-event-waituntil.https.htmlPass6 / 6
service-worker/fetch-audio-tainting.https.htmlPass1 / 1
service-worker/fetch-canvas-tainting-double-write.https.htmlPass1 / 1
service-worker/fetch-canvas-tainting-image-cache.https.htmlPass40 / 40
service-worker/fetch-canvas-tainting-image.https.htmlPass40 / 40
service-worker/fetch-canvas-tainting-video-cache.https.htmlPass40 / 40
service-worker/fetch-canvas-tainting-video-with-range-request.https.htmlFail4 / 5TEST BUGthe range responses from single origin with both opaque and non-opaque responses subtest expects a load error: the opaque (no-cors) first response and the CORS range responses that the service worker fetches from the same cross-origin URL are patched together, as verify a media response specifies for the responses of one origin whatever their CORS mode (https://html.spec.whatwg.org/multipage/media.html#verify-a-media-response, step 9), and the video taints the canvas; Edge (the only browser of wpt.fyi with results) fails this subtest too; the other subtests pass
service-worker/fetch-canvas-tainting-video.https.htmlPass40 / 40
service-worker/fetch-cors-exposed-header-names.https.htmlPass1 / 1
service-worker/fetch-cors-xhr.https.htmlPass41 / 41
service-worker/fetch-csp.https.htmlPass1 / 1
service-worker/fetch-error.https.htmlPass3 / 3
service-worker/fetch-event-add-async.https.htmlPass2 / 2
service-worker/fetch-event-after-navigation-within-page.https.htmlPass2 / 2
service-worker/fetch-event-async-respond-with.https.htmlPass4 / 4
service-worker/fetch-event-handled.https.htmlPass8 / 8
service-worker/fetch-event-network-error.https.htmlPass1 / 1
service-worker/fetch-event-redirect.https.htmlPass56 / 56
service-worker/fetch-event-referrer-policy.https.htmlFail2 / 3TEST BUGthe subtest fetches an http: URL from an https: document and expects the service worker to answer it: the request is blocked as mixed content before the service workers are consulted (https://fetch.spec.whatwg.org/#concept-main-fetch). Chrome, Firefox and Safari fail the subtest in the same way
service-worker/fetch-event-respond-with-argument.https.htmlPass1 / 1
service-worker/fetch-event-respond-with-body-loaded-in-chunk.https.htmlPass1 / 1
service-worker/fetch-event-respond-with-custom-response.https.htmlPass11 / 11
service-worker/fetch-event-respond-with-partial-stream.https.htmlPass1 / 1
service-worker/fetch-event-respond-with-readable-stream-chunk.https.htmlPass1 / 1
service-worker/fetch-event-respond-with-readable-stream.https.htmlPass10 / 10
service-worker/fetch-event-respond-with-response-body-with-invalid-chunk.https.htmlPass1 / 1
service-worker/fetch-event-respond-with-stops-propagation.https.htmlPass1 / 1
service-worker/fetch-event-throws-after-respond-with.https.htmlPass1 / 1
service-worker/fetch-event-within-sw.https.htmlPass2 / 2
service-worker/fetch-event.https.h2.htmlPass7 / 7
service-worker/fetch-event.https.htmlFail42 / 43TEST BUGthe Service Worker responds to fetch event with an existing client id subtest expects event.clientId to be the empty string for the navigation request of an iframe; Create Fetch Event and Dispatch (https://w3c.github.io/ServiceWorker/#create-fetch-event-and-dispatch, step 8) initializes it to the id of the client of the request, which for a navigation is the environment of the document that starts it (https://html.spec.whatwg.org/multipage/browsing-the-web.html#create-navigation-params-by-fetching), as speculation-rules/prefetch/tentative/service-worker expects; Chrome, Firefox and Safari give the empty string; the other subtests pass
service-worker/fetch-frame-resource.https.htmlPass6 / 6
service-worker/fetch-header-visibility.https.htmlPass1 / 1
service-worker/fetch-mixed-content-to-inscope.https.htmlPass1 / 1
service-worker/fetch-mixed-content-to-outscope.https.htmlPass1 / 1
service-worker/fetch-request-body-cancel.https.htmlError1 / 2NOT IMPLEMENTEDthe bodies are not streamed: cancelling event.request.body does not cancel the body of the request
service-worker/fetch-request-css-base-url.https.htmlPass4 / 4
service-worker/fetch-request-css-cross-origin.https.htmlPass4 / 4
service-worker/fetch-request-css-images.https.htmlPass4 / 4
service-worker/fetch-request-fallback.https.htmlPass17 / 17
service-worker/fetch-request-no-freshness-headers.https.htmlPass1 / 1
service-worker/fetch-request-redirect.https.htmlPass35 / 35
service-worker/fetch-request-resources.https.htmlPass67 / 67
service-worker/fetch-request-xhr-sync-error.https.window.jsPass1 / 1
service-worker/fetch-request-xhr-sync-on-worker.https.htmlPass1 / 1
service-worker/fetch-request-xhr-sync.https.htmlPass1 / 1
service-worker/fetch-request-xhr.https.htmlPass13 / 13
service-worker/fetch-response-taint.https.htmlPass132 / 132
service-worker/fetch-response-xhr.https.htmlPass1 / 1
service-worker/fetch-waits-for-activate.https.htmlPass2 / 2
service-worker/fetch-with-body.https.htmlPass1 / 1
service-worker/getregistration.https.htmlPass6 / 6
service-worker/getregistrations.https.htmlPass6 / 6
service-worker/global-serviceworker.https.any.jsPass4 / 4
service-worker/historical.https.any.jsPass1 / 1
service-worker/http-to-https-redirect-and-register.https.htmlPass2 / 2
service-worker/immutable-prototype-serviceworker.https.htmlPass1 / 1
service-worker/import-scripts-cross-origin.https.htmlPass1 / 1
service-worker/import-scripts-data-url.https.htmlPass1 / 1
service-worker/import-scripts-mime-types.https.htmlPass23 / 23
service-worker/import-scripts-redirect.https.htmlPass3 / 3
service-worker/import-scripts-resource-map.https.htmlPass2 / 2
service-worker/import-scripts-updated-flag.https.htmlPass5 / 5
service-worker/indexeddb.https.htmlPass3 / 3
service-worker/install-event-type.https.htmlPass1 / 1
service-worker/installing.https.htmlPass2 / 2
service-worker/intercepted-referrer.https.htmlPass1 / 1
service-worker/interface-requirements-sw.https.htmlPass4 / 4
service-worker/invalid-blobtype.https.htmlPass1 / 1
service-worker/invalid-header.https.htmlPass1 / 1
service-worker/iso-latin1-header.https.htmlPass1 / 1
service-worker/local-url-inherit-controller.https.htmlPass9 / 9
service-worker/mime-sniffing.https.htmlPass1 / 1
service-worker/multi-globals/url-parsing.https.htmlPass3 / 3
service-worker/multipart-image.https.htmlFail3 / 6NOT IMPLEMENTEDmultipart/x-mixed-replace images
service-worker/multiple-register.https.htmlPass3 / 3
service-worker/multiple-update.https.htmlPass1 / 1
service-worker/navigate-window.https.htmlFail1 / 2TEST RUNNERthe subtest of the uncontrolled windows expects the window of the WPT harness (/testharness_runner.html) and the test window as an auxiliary window among the clients; the subtest of the controlled windows passes
service-worker/navigation-headers.https.htmlPass83 / 83
service-worker/navigation-preload/broken-chunked-encoding.https.htmlPass2 / 2
service-worker/navigation-preload/chunked-encoding.https.htmlPass1 / 1
service-worker/navigation-preload/content-encoding.https.htmlPass1 / 1
service-worker/navigation-preload/empty-preload-response-body.https.htmlPass1 / 1
service-worker/navigation-preload/get-state.https.htmlFail2 / 3TEST BUGsetHeaderValue() normalizes the value before checking it (https://w3c.github.io/ServiceWorker/#dom-navigationpreloadmanager-setheadervalue): a leading carriage return is removed, the test expects a TypeError as in the browsers
service-worker/navigation-preload/navigationPreload.https.htmlPass1 / 1
service-worker/navigation-preload/redirect.https.htmlPass4 / 4
service-worker/navigation-preload/request-headers.https.htmlPass1 / 1
service-worker/navigation-preload/resource-timing.https.htmlPass1 / 1
service-worker/navigation-preload/samesite-cookies.https.htmlPass5 / 5
service-worker/navigation-preload/samesite-iframe.https.htmlPass1 / 1
service-worker/navigation-redirect-body.https.htmlPass1 / 1
service-worker/navigation-redirect-resolution.https.htmlPass3 / 3
service-worker/navigation-redirect-to-http.https.htmlPass1 / 1
service-worker/navigation-redirect.https.htmlPass78 / 78
service-worker/navigation-sets-cookie.https.htmlPass16 / 16
service-worker/navigation-timing-extended.https.htmlPass1 / 1
service-worker/navigation-timing-sizes.https.htmlPass3 / 3
service-worker/navigation-timing.https.htmlPass3 / 3
service-worker/nested-blob-url-workers.https.htmlPass3 / 3
service-worker/next-hop-protocol.https.htmlFail1 / 2TEST BUGresources/empty.h2.js is fetched from the origin of the test, the HTTP/1.1 server of port 8443: the .h2. of a resource name does not select the HTTP/2 server of wptserve (only the flags of the test file do), so nextHopProtocol is http/1.1, as the test comment anticipates (Edge passes only the H1 subtest on wpt.fyi)
service-worker/no-dynamic-import-in-module.any.jsPass3 / 3
service-worker/no-dynamic-import.any.jsPass3 / 3
service-worker/onactivate-script-error.https.htmlPass5 / 5
service-worker/oninstall-script-error.https.htmlPass6 / 6
service-worker/opaque-response-preloaded.https.htmlPass2 / 2
service-worker/opaque-script.https.htmlPass4 / 4
service-worker/performance-timeline.https.htmlPass4 / 4
service-worker/postmessage-blob-url.https.htmlPass1 / 1
service-worker/postmessage-from-waiting-serviceworker.https.htmlPass1 / 1
service-worker/postmessage-msgport-to-client.https.htmlPass1 / 1
service-worker/postmessage-to-client-message-queue.https.htmlPass5 / 5
service-worker/postmessage-to-client.https.htmlPass1 / 1
service-worker/postmessage.https.htmlPass5 / 5
service-worker/ready.https.window.jsPass9 / 9
service-worker/redirected-response.https.htmlPass26 / 26
service-worker/referer.https.htmlPass1 / 1
service-worker/referrer-policy-header.https.htmlPass3 / 3
service-worker/referrer-toplevel-script-fetch.https.htmlPass2 / 2
service-worker/register-closed-window.https.htmlPass1 / 1
service-worker/register-default-scope.https.htmlPass3 / 3
service-worker/register-same-scope-different-script-url.https.htmlPass5 / 5
service-worker/register-wait-forever-in-install-worker.https.htmlPass1 / 1
service-worker/registration-basic.https.htmlPass3 / 3
service-worker/registration-end-to-end.https.htmlPass1 / 1
service-worker/registration-events.https.htmlPass1 / 1
service-worker/registration-iframe.https.htmlPass3 / 3
service-worker/registration-mime-types.https.htmlPass39 / 39
service-worker/registration-schedule-job.https.htmlPass3 / 3
service-worker/registration-scope-module-static-import.https.htmlPass3 / 3
service-worker/registration-scope.https.htmlPass10 / 10
service-worker/registration-script-module.https.htmlDisabled–TEST RUNNERthe test waits for a response that a handler delays by 1 s of the virtual clock (resources/invalid-chunked-encoding-with-flush.py) while a service worker job waits for it: the event loop of the runner does not advance the clock while the jobs of the service workers are running, so the clock only advances by the 100 µs of each of its reads, between the waits of the loop. It took ~1.5 s on Linux and macOS, and more than the 60 s limit on Windows, where these waits last a 15.6 ms timer period (now 1 ms: the runner calls timeBeginPeriod(1)); it still exceeded the limit on a loaded macOS machine when the whole suite ran, so the result depends on the load
service-worker/registration-script-url.https.htmlPass8 / 8
service-worker/registration-script.https.htmlDisabled–TEST RUNNERthe test waits for a response that a handler delays by 1 s of the virtual clock (resources/invalid-chunked-encoding-with-flush.py) while a service worker job waits for it: the event loop of the runner does not advance the clock while the jobs of the service workers are running, so the clock only advances by the 100 µs of each of its reads, between the waits of the loop. It took ~1.5 s on Linux and macOS, and more than the 60 s limit on Windows, where these waits last a 15.6 ms timer period (now 1 ms: the runner calls timeBeginPeriod(1)); it still exceeded the limit on a loaded macOS machine when the whole suite ran, so the result depends on the load
service-worker/registration-security-error.https.htmlPass8 / 8
service-worker/registration-service-worker-attributes.https.htmlPass1 / 1
service-worker/registration-updateviacache.https.htmlPass25 / 25
service-worker/rejections.https.htmlPass1 / 1
service-worker/request-end-to-end.https.htmlPass1 / 1
service-worker/resource-timing-bodySize.https.htmlPass24 / 24
service-worker/resource-timing-cross-origin-server-timing.https.htmlFail0 / 1TEST BUGthe test expects the decodedBodySize and encodedBodySize of a CORS response without Timing-Allow-Origin to be 0: the body sizes are CORS-protected, not TAO-protected (https://w3c.github.io/resource-timing/, resource-timing/body-size-cross-origin.https.html). The Server-Timing metrics of the response are not exposed, as the test expects
service-worker/resource-timing-cross-origin.https.htmlFail0 / 2TEST BUGthe test expects the connection times of an entry whose timing allow check fails to equal fetchStart; they are 0 (https://w3c.github.io/resource-timing/). Chrome, Firefox and Safari fail the two subtests on domainLookupStart
service-worker/resource-timing-fetch-variants.https.htmlPass5 / 5
service-worker/resource-timing.sub.https.htmlPass2 / 2
service-worker/respond-with-body-accessed-response.https.htmlPass20 / 20
service-worker/same-site-cookies.https.htmlPass66 / 66
service-worker/sandboxed-iframe-fetch-event.https.htmlPass29 / 29
service-worker/sandboxed-iframe-navigator-serviceworker.https.htmlPass4 / 4
service-worker/secure-context.https.htmlPass1 / 1
service-worker/service-worker-csp-connect.https.htmlPass5 / 5
service-worker/service-worker-csp-default.https.htmlPass5 / 5
service-worker/service-worker-csp-script.https.htmlPass5 / 5
service-worker/service-worker-header.https.htmlPass1 / 1
service-worker/serviceworker-message-event-historical.https.htmlPass1 / 1
service-worker/serviceworkerobject-scripturl.https.htmlPass4 / 4
service-worker/skip-waiting-installed.https.htmlPass1 / 1
service-worker/skip-waiting-using-registration.https.htmlPass2 / 2
service-worker/skip-waiting-without-client.https.htmlPass2 / 2
service-worker/skip-waiting-without-using-registration.https.htmlPass2 / 2
service-worker/skip-waiting.https.htmlPass1 / 1
service-worker/soft-update-fetch-metadata.https.htmlPass3 / 3
service-worker/srcdoc-iframe.https.htmlPass5 / 5
service-worker/state.https.htmlPass1 / 1
service-worker/static-router-cross-origin-navigation.https.htmlPass1 / 1
service-worker/static-router-fetch-event.https.htmlPass2 / 2
service-worker/static-router-invalid-rules.https.htmlPass8 / 8
service-worker/static-router-main-resource.https.htmlPass9 / 9
service-worker/static-router-multiple-router-registrations.https.htmlPass2 / 2
service-worker/static-router-mutiple-conditions.https.htmlPass2 / 2
service-worker/static-router-no-fetch-handler.https.htmlPass3 / 3
service-worker/static-router-race-network-and-fetch-handler.https.htmlPass8 / 8
service-worker/static-router-request-destination.https.htmlPass2 / 2
service-worker/static-router-request-method.https.htmlPass4 / 4
service-worker/static-router-subresource.https.htmlPass18 / 18
service-worker/synced-state.https.htmlPass1 / 1
service-worker/uncontrolled-page.https.htmlPass1 / 1
service-worker/unregister-controller.https.htmlPass3 / 3
service-worker/unregister-immediately-before-installed.https.htmlDisabled–NOT IMPLEMENTEDRuns until the maximum duration of the runner (1 minute): Clear-Site-Data is not implemented, so it cannot abort the evaluation of a service worker script that loops forever
service-worker/unregister-immediately-during-extendable-events.https.htmlFail0 / 1TEST BUGthe fetch of the iframe (frame.contentWindow.fetch()) rejects with a TypeError of the realm of the iframe, as its relevant realm is the one of the iframe, while promise_rejects_js(test, TypeError, ...) expects an instance of the TypeError of the test page: "expected instance of function TypeError()". The fetch does fail: Clear-Site-Data clears the registration and terminates the worker whose respondWith() never settles
service-worker/unregister-immediately.https.htmlPass4 / 4
service-worker/unregister-then-register-new-script.https.htmlPass3 / 3
service-worker/unregister-then-register.https.htmlPass4 / 4
service-worker/unregister.https.htmlPass2 / 2
service-worker/update-after-navigation-fetch-event.https.htmlPass3 / 3
service-worker/update-after-navigation-redirect.https.htmlPass1 / 1
service-worker/update-after-oneday.https.htmlTimeout0 / 1TEST BUGthe test needs a registration whose last update check is older than 24 hours and cannot age it (it relies on a testing hook that the browsers do not expose): it times out in Chrome, Firefox and Safari too
service-worker/update-bytecheck-cors-import.https.htmlPass8 / 8
service-worker/update-bytecheck.https.htmlPass8 / 8
service-worker/update-import-scripts.https.htmlPass5 / 5
service-worker/update-missing-import-scripts.https.htmlPass2 / 2
service-worker/update-module-request-mode.https.htmlPass1 / 1
service-worker/update-no-cache-request-headers.https.htmlPass1 / 1
service-worker/update-not-allowed.https.htmlPass3 / 3
service-worker/update-on-navigation.https.htmlPass1 / 1
service-worker/update-recovery.https.htmlFail0 / 1TEST BUGthe test expects that the iframe of a navigation that fails with a network error (the service worker rejects the request) fires no load event; the iframe fires it for the error document, as in Chrome and Firefox, which fail the test in the same way
service-worker/update-registration-with-type.https.htmlPass7 / 7
service-worker/update-result.https.htmlPass1 / 1
service-worker/update.https.htmlPass7 / 7
service-worker/waiting.https.htmlPass2 / 2
service-worker/websocket-in-service-worker.https.htmlPass1 / 1
service-worker/websocket.https.htmlPass1 / 1
service-worker/webvtt-cross-origin.https.htmlPass10 / 10
service-worker/windowclient-ancestorOrigins.sub.https.htmlPass4 / 4
service-worker/windowclient-navigate.https.htmlFail21 / 22TEST BUGthe subtest expects the frame type of a window opened with window.open() to be "top-level"; its browsing context is an auxiliary browsing context, whose frame type is "auxiliary" (https://w3c.github.io/ServiceWorker/#get-frame-type). Firefox fails the subtest in the same way; the other subtests pass
service-worker/worker-client-id.https.htmlPass1 / 1
service-worker/worker-in-sandboxed-iframe-by-csp-fetch-event.https.htmlPass5 / 5
service-worker/worker-interception-redirect.https.htmlPass66 / 66
service-worker/worker-interception.https.htmlPass16 / 16
service-worker/xhr-content-length.https.window.jsPass5 / 5
service-worker/xhr-response-url.https.htmlPass6 / 6
service-worker/xsl-base-url.https.htmlPass1 / 1

Tentative tests

TestResultSubtestsKindDescription
cache-storage/cross-partition.https.tentative.htmlPass4 / 4
service-worker/partitioned-claim.tentative.https.htmlPass1 / 1
service-worker/partitioned-cookies.tentative.https.htmlPass4 / 4
service-worker/partitioned-getRegistrations.tentative.https.htmlPass1 / 1
service-worker/partitioned-matchAll.tentative.https.htmlPass1 / 1
service-worker/partitioned.tentative.https.htmlPass2 / 2
service-worker/tentative/fetch-event-download-fallback.https.htmlFail0 / 1NOT IMPLEMENTEDthe downloads (<a download>), and the service worker script of the test is not fetched
service-worker/tentative/fetch-event-download-out-of-scope.https.htmlFail0 / 1NOT IMPLEMENTEDthe downloads (<a download>), and the service worker script of the test is not fetched
service-worker/tentative/fetch-event-download-respond-with.https.htmlFail0 / 1NOT IMPLEMENTEDthe downloads (<a download>), and the service worker script of the test is not fetched
service-worker/tentative/fetch-event-download.https.htmlFail0 / 1NOT IMPLEMENTEDthe downloads (<a download>), and the service worker script of the test is not fetched
service-worker/tentative/static-router/static-router-resource-timing.https.htmlPass16 / 16

Reftests

TestResultVariantsKindDescription
service-worker/svg-target-reftest.https.htmlPass1 / 1

Crash tests

TestResultVariantsKindDescription
cache-storage/crashtests/cache-response-clone.https.htmlTimeout0 / 1BUGthe body of a cloned response that is put in the cache is locked (TypeError: The stream is locked), so the test-wait class is never removed
service-worker/detached-register-crash.https.htmlPass1 / 1
service-worker/messageport-transfer-crash.htmlPass1 / 1