Content - befd67cb378b0ea3e0f8d45cad3e344a4e2f9610 - d6d3bc7/service-workers/stub-4.6-cache-objects.html

visit type:

Tip revision: a9a28f3f94de6eae89f0780128b51e52b2d49b01 authored by Chris Nardi on 02 April 2018, 03:04:33 UTC
Update IRC archive link

Tip revision: a9a28f3

stub-4.6-cache-objects.html

<!DOCTYPE html>
<html>
<title>Service Workers: Caches</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#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>

Browse the archive

https://github.com/web-platform-tests/wpt