Content - f6c9ecbd1919553af81429f1e16a6637ccc902f3 - a607e43/service-workers/stub-4.6.1-cache-lifetimes.html

visit type:

Tip revision: b007364596ffd5eba7f7754c44220253bbbf113d authored by Philip Jägenstedt on 11 May 2017, 11:30:46 UTC
Add a test for fully exiting fullscreen due to navigation

Tip revision: b007364

stub-4.6.1-cache-lifetimes.html

<!DOCTYPE html>
<html>
<title>Service Workers: Understanding Cache Lifetimes</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#cache-lifetimes">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

The `[Cache][1]` instances are not part of the browser's HTTP cache. The
`[Cache][1]` objects are exactly what authors have to manage themselves. The
`[Cache][1]` objects do not get updated unless authors explicitly request them
to be. The `[Cache][1]` objects do not expire unless authors delete the
entries. The `[Cache][1]` objects do not disappear just because the Service
Worker script is updated. That is, caches are not updated automatically.
Updates must be manually managed. This implies that authors should version
their caches by name and make sure to use the caches only from the version of
the ServiceWorker that can safely operate on.

[1]: #cache-interface

-->



    <script>
        test(function() {
            // not_implemented();
        }, "There are no tests for section Understanding Cache Lifetimes so far.");
    </script>

    </body>
</html>

Browse the archive

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