Re: [w3c/ServiceWorker] Formalizing a timeout API (#1292)

@jakearchibald true. A `respondWith`/`waitUntil` timeout can certainly be constructed manually, but if a big enough percentage of implementations are guarding `respondWith`/`waitUntil` with a timeout, it might make sense to consider adding it as a built-in feature.

At the end of the day, it would be nice to have some sort of built-in safeguard against locking up a service worker with a never-ending operation. If we just pick one safeguard, I think `skipWaiting({ force: true })` approach makes the most sense, as it doesn't require preemptively guarding.

-- 
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/1292#issuecomment-379114738