| OLD | NEW |
|---|
| (Empty) | |
| 1 <!DOCTYPE html> |
| 2 <html> |
| 3 <title>Service Workers: Caches</title> |
| 4 <head> |
| 5 <link rel="help" href="https://w3c.github.io/ServiceWorker/#cache-object
s"> |
| 6 <script src="/resources/testharness.js"></script> |
| 7 <script src="/resources/testharnessreport.js"></script> |
| 8 |
| 9 </head> |
| 10 <body> |
| 11 |
| 12 <!-- |
| 13 |
| 14 To allow authors to fully manage their content caches for offline use, the |
| 15 `[ServiceWorkerGlobalScope][1]` execution context provides the caching methods |
| 16 largely conforming to [ECMAScript 6 Map objects][2] with additional convenience |
| 17 methods. A domain can have multiple, named `[Cache][3]` objects, whose contents |
| 18 are entirely under the control of scripts. Caches are not shared across |
| 19 domains, and they are completely isolated from the browser's HTTP cache. |
| 20 |
| 21 [1]: #service-worker-global-scope-interface |
| 22 [2]: http://goo.gl/gNnDPO |
| 23 [3]: #cache-interface |
| 24 |
| 25 --> |
| 26 |
| 27 |
| 28 |
| 29 <script> |
| 30 test(function() { |
| 31 // not_implemented(); |
| 32 }, "There are no tests for section Caches so far."); |
| 33 </script> |
| 34 |
| 35 </body> |
| 36 </html> |
| 37 |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2415873002:
Import w3c tests for the service workers (Closed)
