|  | <!DOCTYPE html> | 
|  | <html> | 
|  | <title>Service Workers: Caches</title> | 
|  | <head> | 
|  | <link rel="help" href="https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#cache-objects"> | 
|  | <script src="/resources/testharness.js"></script> | 
|  | <script src="/resources/testharnessreport.js"></script> | 
|  |  | 
|  | </head> | 
|  | <body> | 
|  |  | 
|  | <!-- | 
|  |  | 
|  | To allow authors to fully manage their content caches for offline use, the | 
|  | `[ServiceWorkerGlobalScope][1]` execution context provides the caching methods | 
|  | largely conforming to [ECMAScript 6 Map objects][2] with additional convenience | 
|  | methods. A domain can have multiple, named `[Cache][3]` objects, whose contents | 
|  | are entirely under the control of scripts. Caches are not shared across | 
|  | domains, and they are completely isolated from the browser's HTTP cache. | 
|  |  | 
|  | [1]: #service-worker-global-scope-interface | 
|  | [2]: http://goo.gl/gNnDPO | 
|  | [3]: #cache-interface | 
|  |  | 
|  | --> | 
|  |  | 
|  |  | 
|  |  | 
|  | <script> | 
|  | test(function() { | 
|  | // not_implemented(); | 
|  | }, "There are no tests for section Caches so far."); | 
|  | </script> | 
|  |  | 
|  | </body> | 
|  | </html> | 
|  |  |