Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
Revision a1b9c9f70005a294db1938a8280f3b784e7c99a0 authored by Anne van Kesteren on 29 November 2016, 17:33:31 UTC, committed by Anne van Kesteren on 29 November 2016, 17:33:31 UTC 
clear cookies
1 parent 1304d51
Raw File
Tip revision: a1b9c9f70005a294db1938a8280f3b784e7c99a0 authored by Anne van Kesteren on 29 November 2016, 17:33:31 UTC
clear cookies
Tip revision: a1b9c9f
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