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

My mistake. Looks like an implementation bug (Chrome) rather than the spec:-

 function reply(result){
  console.log("In reply", replied);
  if (replied) return;
  console.log("After reply", replied);
  
  replied = true;
  event.respondWith(result);
  console.log("Replied : ", replied);
 }

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. Anyway, I'll check with the Chrome people.

BTW Are any of those flags (fetchEvent.repondedTo would be useful) exposed? bodyUsed is good for request/response but event state could be good? 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.

And what happened to FetchEvent.ClientId?

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