Re: [w3c/manifest] Add a unique identifier for a PWA (#586)

Note, I expect we will need an identifier mechanism for service workers as well for similar use cases; e.g. migrating from one scope to another.  It would be difficult for sites to manage the teardown of one service worker and migration to another without something like this.

Do you plan to make your proposal work for service workers as well?

The strawman I had been thinking of was something lile:

```
navigator.serviceWorker.register('sw.js', {
  scope: '/some/scope',
  token: 'my-origin-unique-token',
});
```

So if you call register again with the same token, but a different scope we would migrate the current service worker registration to the new scope.

-- 
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/manifest/issues/586#issuecomment-608515891