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

> Well, the original proposal of the SW acting as its own client, with some APIs opting out of that, would essentially give you that.

The service worker holds itself alive as a Client?  That sounds extremely leak prone.

If we really want to go the route of no client, but its still a subresource load (ignoring that subresource implies its a sub- of a client), then I'd suggest we:

1) Distill out the concepts from the client subresource interception into a new concept.
2) Re-write current subresource loads to use that new concept.
3) Write notifications to use the new concept as well.

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