Re: [ServiceWorker] Fetch API respondWith's implicit RETURN (#844)

> If I stick "replied = true" after the respondWith call then the PC never gets there. It's like the SP gets set to caller - 1 rather than caller.

I don't know what PC and SP stand for here. Your code example looks like it's relying on global state (where is `replied` coming from?), if it is, that's likely your source of bugs.

> BTW Are any of those flags (fetchEvent.repondedTo would be useful) exposed?

Out of curiosity, what would you use it for?

> Having said that I'm still not comfortable doing a FETCH in a FETCH event and not expecting recursion but I'm a beginner at the FETCH API.

Fetches within a service worker do not trigger fetch events within the same service worker.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/844#issuecomment-195355217

Received on Friday, 11 March 2016 13:01:46 UTC