mirror of
https://github.com/servo/servo.git
synced 2025-07-10 00:43:39 +01:00
46 lines
1.3 KiB
HTML
46 lines
1.3 KiB
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>
|
|
|