Re: [w3c/ServiceWorker] provide a way to execute work after browser has consumed a response (#1397)

> * FetchEvent.handled

handled has the advantage to relate to the "Handle Fetch" algorithm.
This seems to map well with the idea to do some JS processing at the end of this algorithm.

> I don't think we can differentiate between a direct Response being passed vs a Promise-to-Response.

Agreed and I do not see a need to separate this case in smaller cases.
The 3 cases (valid response, error, go to network) seem ok.
 Note that the 'error' case would also include the case of not calling respondWith but cancelling the event.

-- 
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/1397#issuecomment-479649393