Re: [whatwg/fetch] Only specific APIs should skip the fetch event when called within a service worker (#303)

I guess it feels a bit of a foot gun to me.  Devs have to understand which API call might possibly have self-interception and carefully avoid fetch loops.

I am also reminded about my other annoyance with this change.  We used to be able to say FetchEvent was triggered by either navigation or a request from a controlled client.  We now have a third condition which just feels weird.

Anway, even if we made the notification a Client, we would still have the same problem here.  I think we could even get this kind of loop by a fetch event handler doing `clients.openWindow()` triggering another FetchEvent, etc.

So I guess the timer thing is ok.

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