Re: [w3c/ServiceWorker] consider allowing a non-scope identifier for registrations (#1512)

I would like to move forward on this with the following:

1. `id` value permits any kind of string.  It does not have to be a URL like `scope`.
2. `id` defaults to `scope` value.
3. Spec will be updated to operate on `id` value everywhere we currently use `scope` for the identifier.
4. Moving a registration to a scope that exactly matches another existing registration will replace that registration.  From an API perspective this is similar to calling register() again on the same scope with a different script URL, etc.  I think throwing would be unexpected.

@jakearchibald @youennf @asutherland @jungkees please let me know if you have any comments or concerns with this.  Thanks!

-- 
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/1512#issuecomment-666454901