We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the 2.1. Service Worker section, the spec said
2.1. Service Worker
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
3.1. ServiceWorker
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?
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
@jungkees Thanks for the information! I'll keep an eye on the issue.
No branches or pull requests
In the
2.1. Service Worker
section, the spec saidHowever, in its interface specification which is
3.1. ServiceWorker
section, it saidIf the ServiceWorkerState is associated to service worker's state, I think maybe one of them is incorrect?
Maybe the parsed is redundant now?
The text was updated successfully, but these errors were encountered: