Skip to main content

Browse the archive

Revision 6668ff3716086d3f8efead0f5db2d8d2864c3563 authored by Robert Ma on 21 March 2018, 17:35:46 UTC, committed by Robert Ma on 21 March 2018, 17:35:46 UTC 
Fix resources/test (when running locally)
 
1. Check the HTTP port of wptserve instead of HTTPS to avoid the
   unnecessary complexities of setting up SSL context (which may fail in
   some environments).
2. Use exponential backoff when waiting for wptserve and specify a
   maximum retry to avoid indefinite hang.
3. Use `terminate` instead of `kill` to give wptserve a chance to clean
   up, which is especially useful when running locally.
1 parent dbb38a6
Raw File
stub-3.2.1-navigator-service-worker-installing.html 
<!DOCTYPE html>
<html>
<title>Service Workers: installing</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#navigator-service-worker-installing">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

`navigator.serviceWorker.installing` must return a [ServiceWorker][1] object
representing the [installing worker][2] that is currently undergoing the
installation process (from step 1 to step 7 of the [_Installation
algorithm][3]) for the given [URL scope][4] in which the document may be
[controlled][5] when the Service Worker becomes the [active worker][6].
`navigator.serviceWorker.installing` returns `null` if no Service Worker
[registration][7] is in the [installation process][8].

[1]: #service-worker-interface
[2]: #installing-worker
[3]: #installation-algorithm
[4]: #url-scope
[5]: #document-control
[6]: #active-worker
[7]: #service-worker-registration-internal-interface
[8]: #installation-process

-->



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

    </body>
</html>
back to top