Re: [ServiceWorker] setTimeout/setInterval are unreliable in ServiceWorkers (#838)

I agree that a timeout on fetch would be helpful too, but not enough. 
To elaborate on the use case I was trying to describe:

1. Fetch event comes in, fire off network fetch and start timeout.
2. After 100ms timeout triggers, resolve promise passed to respondWith with something (but leave a waitUntil promise unresolved)
3. When fetch finishes, store its result in cache, postMessage to client to inform it of newly available data, resolve waitUntil promise.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/838#issuecomment-187457787