Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service worker installation uses an algorithm (Start Register) that doesn't exist in SW spec #789

Open
mgiuca opened this issue Sep 12, 2019 · 0 comments · May be fixed by #792

Comments

@mgiuca
Copy link
Collaborator

commented Sep 12, 2019

Invoke Start Register with scope and src members of the registration, a new promise, client, manifest URL, plus the type and update_via_cache members of the registration, in which case the state of the settled promise determines whether the installation succeeded or not.

There is no "Start Register" in the SW spec. As far as I can tell, the nearest thing would be to simply invoke the register() method.

I'm also not sure why this method would (ever) have taken the manifest URL. If we can avoid passing the manifest URL, then we don't need to store it in this algorithm.

Also note that this feature doesn't seem to have been implemented by any user agent, so it is considered "at risk" (though I still believe it would be useful which is why I haven't pushed to deleted it yet).

@mgiuca mgiuca self-assigned this Sep 12, 2019
mgiuca added a commit to mgiuca/manifest that referenced this issue Sep 13, 2019
@mgiuca mgiuca referenced a pull request that will close this issue Sep 13, 2019
1 of 5 tasks complete
mgiuca added a commit to mgiuca/manifest that referenced this issue Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.