Addressing the multiple scopes issue, was: [blink-dev] Intent to Ship: Service Worker's skipWaiting and oncontrollerchange

[Dimitri Glazkov]

On Mon, Dec 15, 2014 at 3:35 PM, Philip Jägenstedt <phi...@opera.com> wrote:

However, the multiple scopes issue is unfortunate, see also Ehsan's
message to blink-dev in October:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/QfxPGw0kJW8/Xm67_ftW3jgJ

The thread quickly died, and AFAICT the risk of shipping incompatible
implementations remains. The GitHub issue has seen recent activity,
but prioritizing its resolution would be helpful.

Alex, Kenji -- what's the latest here? How can we help resolve this?

:DG<

 

[Alex Russell]

We're continuing to discuss what multiple scopes for a single registration might mean; there are design alternatives that don't require any changes to the current system and the result of our last meeting was that there is agreement to add API to allow changes to the existing registration inside the activation step of installation.

See: https://github.com/slightlyoff/ServiceWorker/issues/566