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

The use case sounds reasonable here, and I'd expect there would be more such needs in future.

Basically, I don't think we want to change the base rule that requests initiated from a service worker won't go through a service worker by default. So, I believe we need an optional parameter to fetch that'd override this behavior.

@annevk, maybe we'll need to discuss more on this in line with the https://github.com/whatwg/html/pull/322 where we try to move the active worker definition to Document/WorkerGlobalScope. I remember you sort of proposed replacing the skip-service-worker flag with using the active worker internal slot of a request's client or something like that?

---
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-234890200

Received on Monday, 25 July 2016 08:44:39 UTC