[[Activate]] issue after .replace()?

[seanlong]

In spec [[Activate]] algorithm:

8.5 [[Activate]]
...
3. Let exitingWorker be registration.activeWorker.
4. If exitingWorker is not null, then:
    1. Wait for exitingWorker to finish handling any in-progress requests.
     ...

Issue condition:

1. /foo.html started with sw_v1 (scope is default '/*');
2. a registration is triggered from /bar.html like navigator.serviceWorker.register('sw_v2.js', {scope: '/foo.html'}), and sw_v2.js calls .replace() in oninstall() to trigger replacement;

Problem:
The "registration" used by step 2 is not the one used by the running foo.html, which means the "registration.activeWorker" will be null here.
Then the possible running sw_v1 worker will be replaced without 8.5.4 steps.

Should we also terminate all running workers matches the registration.scope when .replace() is called?

[jungkees]

Thanks for spotting this. I'll be working on it.

[KenjiBaheux]

@jungkees is this still current? Does the required change qualify as Impact MVP or is it merely spec details with no fundamental behavior changes?

[KenjiBaheux]

Replace is not in scope for v1

[jungkees]

Addressed: 4610eac. Thanks!