Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(14)

Side by Side Diff: third_party/WebKit/LayoutTests/imported/wpt/service-workers/stub-4.6.1-cache-lifetimes.html

Issue 2415873002: Import w3c tests for the service workers (Closed)
Patch Set: Rebase Created 4 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 <!DOCTYPE html>
2 <html>
3 <title>Service Workers: Understanding Cache Lifetimes</title>
4 <head>
5 <link rel="help" href="https://w3c.github.io/ServiceWorker/#cache-lifeti mes">
6 <script src="/resources/testharness.js"></script>
7 <script src="/resources/testharnessreport.js"></script>
8
9 </head>
10 <body>
11
12 <!--
13
14 The `[Cache][1]` instances are not part of the browser's HTTP cache. The
15 `[Cache][1]` objects are exactly what authors have to manage themselves. The
16 `[Cache][1]` objects do not get updated unless authors explicitly request them
17 to be. The `[Cache][1]` objects do not expire unless authors delete the
18 entries. The `[Cache][1]` objects do not disappear just because the Service
19 Worker script is updated. That is, caches are not updated automatically.
20 Updates must be manually managed. This implies that authors should version
21 their caches by name and make sure to use the caches only from the version of
22 the ServiceWorker that can safely operate on.
23
24 [1]: #cache-interface
25
26 -->
27
28
29
30 <script>
31 test(function() {
32 // not_implemented();
33 }, "There are no tests for section Understanding Cache Lifetimes so far. ");
34 </script>
35
36 </body>
37 </html>
38
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698