Re: [whatwg/fetch] Resource fetches for notifications shown from a service worker should trigger onfetch (#303)

Workers & shared workers are their own client, so they'd do through their own SW (which may be the same one).

Wouldn't `EventSource`'s retry behaviour make this really complicated? I suppose it's no more complicated than ensuring a SW can't keep itself alive by triggering fetches on itself.

Cases we don't want to loop back through fetch:

* `fetch` - although we could expose the `skipSerivceWorker` option which defaults to true in a SW, but could be explicitly set to false
* `cache.add`, `cache.allAll`
* `importScripts`
* `import`, but we may allow it for dynamic module loading if that lands


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/303#issuecomment-237500307