Re: [ServiceWorker] Can Cache.add() committing at response resolution lead to duplicate requests? (#361)

> So now we settled on the behavior @wanderview suggested: #361 (comment).
>
> @wanderview do you still have a concern about #665? Can I close both issues?

Implementing that behavior sounds reasonable to me, but I think perhaps something is still missing.

For example, I don't see where the incumbent record is cleared for a fetch record when the new response body completes.  It seems the old incumbent should be dropped then.  Am I missing it?

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