New issue
Advanced search Search tips

Issue 878148 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[WPT] [service workers] Don't rely on state in service worker tests for SAB and WASM.

Project Member Reported by binji@chromium.org, Aug 27

Issue description

See https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/external/wpt/html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/resources/serviceworker-failure.js?l=4

Comment from mek@:

"any relying on state is potentially fragile, since the SW can get killed in between. Ideally you'd call waitUntil on the event from which you set state and then resolve the promise you passed to that from the event where you do something with the state."
 
Labels: -OS-Linux
Summary: [WPT] [service workers] Don't rely on state in service worker tests for SAB and WASM. (was: [WPT] [service workers] Don't rely on state in service worker tests)
Many tests in external/wpt/service-workers/service-worker cheat here.

I'll scope this bug to html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/ and wasm/serialization/resources/serviceworker-failure.js.

Sign in to add a comment