summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/service-workers/stub-4.7.1.1-wait-until-method.html
blob: 318318b13940cd9f5f8ebab8b93b6ec371ffb3ff (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
<!DOCTYPE html>
<html>
<title>Service Workers: event.waitUntil(f)</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#wait-until-method">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`event.waitUntil(f)` method, when called in `oninstall` or `onactivate`,
extends the lifetime of the event. When called in `oninstall`, it delays
treating the installing worker until the passed [Promise][1] resolves
successfully. This is primarily used to ensure that a `ServiceWorker` is not
active until all of the core caches it depends on are populated. When called in
`onactivate`, it delays treating the activating worker until the passed
[Promise][1] resolves successfully. This is primarily used to ensure that any
[Functional events][2] are not dispatched to the `ServiceWorker` until it
upgrades database schemas and deletes the outdated cache entries.

[1]: http://goo.gl/3TobQS
[2]: #functional-events

-->



    <script>
        test(function() {
            // not_implemented();
        }, "There are no tests for section event.waitUntil(f) so far.");
    </script>

    </body>
</html>