- From: Jungkee Song <notifications@github.com>
- Date: Wed, 22 Mar 2017 18:45:00 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 23 March 2017 01:45:35 UTC
The "corner case" scenario that I brought in the OP is: A registration R has both the active worker SW1 and the waiting worker SW2, and the instruction sequence occur as follows. 1. The reserved client gets a controller SW1 through [Handle Fetch](https://w3c.github.io/ServiceWorker/#handle-fetch) step 14.6, and SW1 is serving the fetch event for the reserved client's main resource. 1. SW2 executes `skipWaiting()` so SW2 becomes the active worker and SW1 gets to redundant state. 1. SW2 executes `claim()`. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1090#issuecomment-288592736
Received on Thursday, 23 March 2017 01:45:35 UTC