Content - 47b493534240bcb0e125f165c207e6b7195e4440 - a7b4acb/service-workers/stub-3.1.1-service-worker-scope.html

visit type:

Tip revision: 351d25746440b28916e0039b7369a3da4ce3e9a9 authored by plehegar on 21 June 2016, 21:14:03 UTC
Add test for onvisibilitychange

Tip revision: 351d257

stub-3.1.1-service-worker-scope.html

<!DOCTYPE html>
<html>
<title>Service Workers: scope</title>
    <head>
        <link rel="help" href="https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#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>

Browse the archive

https://github.com/web-platform-tests/wpt