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

Spec of Service Worker state #1256

Closed
CYBAI opened this issue Jan 1, 2018 · 2 comments
Closed

Spec of Service Worker state #1256

CYBAI opened this issue Jan 1, 2018 · 2 comments

Comments

@CYBAI
Copy link
Contributor

CYBAI commented Jan 1, 2018

In the 2.1. Service Worker section, the spec said

A service worker has an associated state, which is one of parsed, installing, installed, activating, activated, and redundant. It is initially parsed.

However, in its interface specification which is 3.1. ServiceWorker section, it said

enum ServiceWorkerState {
  "installing",
  "installed",
  "activating",
  "activated",
  "redundant"
};

A ServiceWorker object has an associated ServiceWorkerState object which is itself associated with service worker's state.

If the ServiceWorkerState is associated to service worker's state, I think maybe one of them is incorrect?
Maybe the parsed is redundant now?

@jungkees
Copy link
Collaborator

jungkees commented Jan 2, 2018

Thanks for filing this. This is indeed a dupe of #1162. We'll track it there.

FYI, currently, parsed is a state that isn't exposed to script, but we see some possibility to expose this initial state as #1162 and #1077 suggest.

@jungkees jungkees closed this as completed Jan 2, 2018
@CYBAI
Copy link
Contributor Author

CYBAI commented Jan 2, 2018

@jungkees Thanks for the information! I'll keep an eye on the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants