summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/service-workers/stub-3.1.1-service-worker-scope.html
blob: 8c75c608297a3dcf14d03d60ebc624ea233b6427 (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
40
41
42
43
44
45
46
<!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>