Re: [w3c/ServiceWorker] async waitUntil() does not allow extension on final promise resolution? (#1039)

I think there might be confusion here, looking at some of the examples. Given the following:

```js
e.waitUntil(p);

const q = p.then(() => {
  e.waitUntil(r);
});
```

My impression is that the OP wants to wait until `q` and `r`, i.e. on the two different things passed to `waitUntil`. This seems very reasonable and easy to accomplish (using only the public API). It also matches https://github.com/jakearchibald/async-waituntil-polyfill/.

However, the implementation in #1049 is doing something completely different: it's waiting on `p` **and `q`**. Waiting on `q` is not very reasonable, because `q` is never passed to `waitUntil`, and can only be discovered by crawling the promise graph.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1039#issuecomment-270826618