Currently it can be difficult to iteratively develop a new service worker because its tricky to get the new worker running. In particular, if you have an existing service worker that is controlling the page your developing, refreshing the page may not update the service worker. This happens because the active worker is not removed as long as there is a controlled client. Now, web developers can work around this by manually close the controlled client or by using skipWaiting() in their service worker. It would be nice, though, if devtools could provide something to make this work easier. The first step towards that end would be providing a way for devtools to indicate that a client should stop being controlled. There could be a number of different UX options here: * On about:debugging list the controlled clients in an expanding list. A "stop controlling" button could be next to each client. * On about:debugging provide a "force upgrade" option which stops controlling all clients and then triggers an update.