summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html
blob: 6981d3079c3e108d6f4c96a69db719e206d09c75 (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
<!DOCTYPE html>
<html>
<title>Service Workers: event.replace()</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#replace-method">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`replace()` interacts with `waitUntil` method in the following way:

-   Successful installation can be delayed by `waitUntil`, perhaps by
    subsequent event handlers.
-   Replacement only happens upon successful installation
-   Therefore, replacement of the [active worker][1] (if any) is not
    immediate, however it may occur as soon as the end of the current turn.



[1]: #navigator-service-worker-active

-->



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

    </body>
</html>