-
Notifications
You must be signed in to change notification settings - Fork 161
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
Adding service workers to specs #3
Comments
Brain fart: The cache could be built dynamically. Eg, the cache name could be Once a new version of the spec is discovered, the old cache is deleted. It's not as atomic as handling everything in install/activate events but it could work for simple pages like specs. |
Part of whatwg/meta#3. This allows any standard using the shared deploy script to automatically get a service worker generated, which delegates all of its logic to a shared file on resources.whatwg.org. It allows room for future expansions of the deploy script to include extra resources. This still requires registering the generated service worker in each spec's HTML, however.
Part of whatwg/meta#3. This allows any standard using the shared deploy script to automatically get a service worker generated, which delegates all of its logic to a shared file on resources.whatwg.org. It allows room for future expansions of the deploy script to include extra resources. This still requires registering the generated service worker in each spec's HTML, however.
Part of whatwg/meta#3. This allows any standard using the shared deploy script to automatically get a service worker generated, which delegates all of its logic to a shared file on resources.whatwg.org. It allows room for future expansions of the deploy script to include extra resources. This still requires registering the generated service worker in each spec's HTML, however.
This was deployed successfully for whatwg/dom in whatwg/dom#476. I'll update the OP with a checklist. Note that resources apart from the default set won't be cacheable without more deploy script work in the vein of #11. |
This was done for everything but HTML as part of #23. (As noted there, Encoding is currently blocked; see whatwg/encoding#132.) We'll leave this open to track HTML though. |
Now that Encoding is done, maybe this should move to html-build or html directly? |
Specs to add service worker to:
Special:
Easy:
Need to start using the deploy script first (#11):
The best path here might be to fix #11, then add the service worker registration to the Bikeshed template, instead of doing individual PRs like whatwg/dom#476
Original post follows:
I did this for streams with some success in whatwg/streams#637. Some thoughts:
self.toCache = ...
or maybe we could even get rid of that by inferring the logo filename from the origin.The text was updated successfully, but these errors were encountered: