[wpt-sync] Sync PR 15852 - service worker: Improve WPT tests for async respondWith/waitUntil.
Categories
(Core :: DOM: Service Workers, enhancement, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 15852 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/15852
Details from upstream follow.
Matt Falkenhagen <falken@chromium.org> wrote:
service worker: Improve WPT tests for async respondWith/waitUntil.
See discussion at [1] and [2].
This makes the following changes.
Adds a test for:
self.addEventListener('fetch', e => {
Promise.resolve().then(() => {
e.respondWith(new Response('hi'));
});
});This should not throw because respondWith() is called while the event
dispatch flag is still set.The microtask checkpoint is in "Cleanup After Running Scripts" here:
https://html.spec.whatwg.org/multipage/webappapis.html#clean-up-after-running-scriptThis is called from step 16.2 here:
https://heycam.github.io/webidl/#call-a-user-objects-operationWhich in turn is called from the DOM spec's "Inner Invoke" to call event
targets:
https://dom.spec.whatwg.org/#concept-event-listener-inner-invoke
Changes the expectation for:
addEventListener('message', event => {
Promise.resolve().then(event.waitUntil(p));
});From throws to not throws, for the same reasoning as above.
Changes the expectation for:
addEventListener('message', event => {
waitPromise = Promise.resolve();
event.waitUntil(waitPromise);
waitPromise.then(() => {
Promise.resolve().then(() => {event.waitUntil();});
});
});From throws to not throws. This is subtle. Because all the promises
are just Promise.resolve(), the event dispatch flag is still set
by the time the second waitUntil() is called.
To test what 3. originally intended, a new test is
added which makes waitPromise a promise that does not immediately
resolve.
Changes the expectation for:
addEventListener(‘fetch’, event => {
response = Promise.resolve(new Response('RESP'));
event.respondWith(response);
response.then(() => {
Promise.resolve().then(() => {event.waitUntil();});
})
});Again this is because the promises used resolve immediately,
so the event dispatch flag is still set.Similarly, a new test is added to cover the original intent.
These WPT changes appear to match the behavior of Safari and Edge while
diverging from Chrome and (partially) Firefox.[1] https://github.com/w3c/ServiceWorker/issues/1213
[2] https://github.com/w3c/ServiceWorker/issues/1394Bug: 942414
Change-Id: I9a4a56d71d3919ed614ff78df2bdc6cc0251dadd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1524393
Commit-Queue: Matt Falkenhagen \<falken@chromium.org>
Reviewed-by: Ben Kelly \<wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#641514}
| Assignee | ||
Updated•7 years ago
|
| Assignee | ||
Updated•7 years ago
|
| Assignee | ||
Updated•7 years ago
|
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Comment 3•7 years ago
|
||
Comment 6•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/a941738d800e
https://hg.mozilla.org/mozilla-central/rev/4943b28c0d72
https://hg.mozilla.org/mozilla-central/rev/b4b704c52ae9
https://hg.mozilla.org/mozilla-central/rev/a89c195336d4
Description
•