[WPT] [service workers] Don't rely on state in service worker tests for SAB and WASM. |
||
Issue descriptionSee 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."
,
Aug 28
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.
,
Aug 28
As the comment was made on https://chromium-review.googlesource.com/c/chromium/src/+/1175490 |
||
►
Sign in to add a comment |
||
Comment 1 by binji@chromium.org
, Aug 27