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

> does it solve your concerns if we add a new client type of "serviceworker"?

Well, it seems we should do that for foreign fetch anyway.  So that is ok.

What protections will we have to prevent a SW from keeping itself alive infinitely via fetch events if it can generate its own fetch event?  We must provide some keep-alive budget so that work can be done, but we don't want this to be a way to persist the SW in memory for long periods.

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