diff options
| author | Matt A. Tobin <mattatobin@localhost.localdomain> | 2018-02-02 04:16:08 -0500 |
|---|---|---|
| committer | Matt A. Tobin <mattatobin@localhost.localdomain> | 2018-02-02 04:16:08 -0500 |
| commit | 5f8de423f190bbb79a62f804151bc24824fa32d8 (patch) | |
| tree | 10027f336435511475e392454359edea8e25895d /testing/web-platform/tests/service-workers/stub-4.6.1-cache-lifetimes.html | |
| parent | 49ee0794b5d912db1f95dce6eb52d781dc210db5 (diff) | |
| download | UXP-5f8de423f190bbb79a62f804151bc24824fa32d8.tar UXP-5f8de423f190bbb79a62f804151bc24824fa32d8.tar.gz UXP-5f8de423f190bbb79a62f804151bc24824fa32d8.tar.lz UXP-5f8de423f190bbb79a62f804151bc24824fa32d8.tar.xz UXP-5f8de423f190bbb79a62f804151bc24824fa32d8.zip | |
Add m-esr52 at 52.6.0
Diffstat (limited to 'testing/web-platform/tests/service-workers/stub-4.6.1-cache-lifetimes.html')
| -rw-r--r-- | testing/web-platform/tests/service-workers/stub-4.6.1-cache-lifetimes.html | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/testing/web-platform/tests/service-workers/stub-4.6.1-cache-lifetimes.html b/testing/web-platform/tests/service-workers/stub-4.6.1-cache-lifetimes.html new file mode 100644 index 000000000..f6c9ecbd1 --- /dev/null +++ b/testing/web-platform/tests/service-workers/stub-4.6.1-cache-lifetimes.html @@ -0,0 +1,38 @@ +<!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> + |