The Cache API for Service Worker consists of additional ServiceWorker APIs which allow authors to fully and conveniently manage their content caches for offline use. An origin can have multiple, named Cache objects, whose contents are entirely under the control of Service Worker scripts. One noteworthy edge that the Cache API has over the polyfill approach is its ability to handle opaque response.
We're proposing to ship a subset of what is defined in the spec (see this document for more details).
Link to “Intent to Implement” blink-dev discussion
The spec and project used to be called Navigation Controller, but the name was changed to Service Worker. See also the Service Worker intent to ship.
Is this feature supported on all five Blink platforms (Windows, Mac, Linux, Chrome OS and Android)?
This is essentially the same demo featured in our Service Worker intent to ship (the demo uses a polyfill and is being updated to let native Cache APIs take over when available).
Developers can check the existence of caches and peek inside manually by inspecting the relevant Service Worker and issuing commands via the console.
Pluses and minuses:
+ There's a first public working draft of the spec.
+ Mozilla is implementing Service Workers in Firefox, see bug 940273.
+ We semi-regularly reconcile the spec and our implementation. We have a defined process for that.
+ The team has been writing W3C testharness.js tests which we plan to upstream to W3C.
+ All the relevant closed or decided cache spec issues are tracked at crbug.com and triaged to minimize compatibility risk (unresolved impact MVP = 0; closed not tracked = 0; decided not tracked = 0; untriaged or unresolved = 0)
+ Based on observations from the spec issue triaging process, we believe that the scope of this intent to ship is fairly stable.
- We could not find any relevant tests in Firefox’s maple branch to cross check our Cache API implementation against
- The spec is under active development
OWP launch tracking bug?
Link to entry on the feature dashboard
Are these available anywhere yet? I would love to try them out against what I have for gecko.
Just to clarify, you're only going to be exposing Caches on the ServiceWorker global for now, right?