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

Hmm, but if its not an atomic replace, then the only value in doing it natively over in user js would be doing an immediate purge of the conflicting registration.  But the purge PR in #1506 is not landed yet.  And if it did land, we could just expose an `unregister({ immediate: true })` which would let js implement their own logic.

So I guess ignore the last comment.  I will not pursue the scopeConflict option for now.

-- 
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-673658617