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.

Sign up for GitHub

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

Jump to bottom

Why is required a page reload to enable SW controlling? #583

Closed
h2non opened this issue Dec 10, 2014 · 2 comments
Closed

Why is required a page reload to enable SW controlling? #583

h2non opened this issue Dec 10, 2014 · 2 comments

Comments

@h2non
Copy link

h2non commented Dec 10, 2014

This disgusting limitation could be removed in a future?
It is a Chromium specific limitation or it is pretended and it must be imposed to all browsers implementations?
There's a fundamental reason about "why"?
@h2non h2non changed the title Why is required a page reload to enable SW controller? Why is required a page reload to enable SW controllering? Dec 10, 2014
@h2non h2non changed the title Why is required a page reload to enable SW controllering? Why is required a page reload to enable SW controlleing? Dec 10, 2014
@h2non h2non changed the title Why is required a page reload to enable SW controlleing? Why is required a page reload to enable SW controlling? Dec 10, 2014
@jakearchibald
Copy link
Contributor

Giving a serviceworker control over a page it didn't have the opportunity to create is opt in. skipWaiting was the first part of this story.

@jakearchibald
Copy link
Contributor

Opened #586 for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@h2non @jakearchibald