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.1.1-service-worker-scope.html 
<!DOCTYPE html>
<html>
<title>Service Workers: scope</title>
    <head>
        <link rel="help" href="https://w3c.github.io/ServiceWorker/#service-worker-scope">
        <script src="/resources/testharness.js"></script>
        <script src="/resources/testharnessreport.js"></script>

    </head>
    <body>

<!--

The `scope` of a `ServiceWorker` object reflects the [URL scope][1] of the
associated Service Worker [registration][2]. The `scope` attribute must return
the [serialization][3] of the URL representing the [URL scope][1] of the
associated Service Worker [registration][2].

For example, consider a document created by a navigation to
`https://example.com/app.html` which [matches][4] via the following
registration call which has been previously executed:
// Script on the page https://example.com/app.html
navigator.serviceWorker.register("/service_worker.js", { scope: "/*" });
The value of `navigator.serviceWorker.controller.scope` will be
`"https://example.com/*"`.



[1]: #url-scope
[2]: #registration
[3]: http://url.spec.whatwg.org/#concept-url-serializer
[4]: #on-fetch-request-algorithm

-->



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

    </body>
</html>
back to top