| Index: third_party/WebKit/LayoutTests/imported/wpt/service-workers/stub-4.6.1-cache-lifetimes.html
|
| diff --git a/third_party/WebKit/LayoutTests/imported/wpt/service-workers/stub-4.6.1-cache-lifetimes.html b/third_party/WebKit/LayoutTests/imported/wpt/service-workers/stub-4.6.1-cache-lifetimes.html
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..f6c9ecbd1919553af81429f1e16a6637ccc902f3
|
| --- /dev/null
|
| +++ b/third_party/WebKit/LayoutTests/imported/wpt/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>
|
| +
|
|
|
Chromium Code Reviews
Issue 2415873002:
Import w3c tests for the service workers (Closed)
