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

1) Client subresource seems to basically take the active worker of the client and go from there. Per https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#on-fetch-request-algorithm anyway there seems to be nothing to it. But that leads to the situation of the SW acting as its own client which you didn't want.

Although I'm not entirely sure why. There seem to be many ways to end up in loops regardless.

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