Replace instances of old ServiceWorker specification URL with new one

The old specification URL is
https://slightlyoff.github.io/ServiceWorker/spec/service_worker/ has
been replaced by the new one at https://w3c.github.io/ServiceWorker/.
This commit is contained in:
Vignesh Sarma K (വിഘ്നേഷ് ശ൪മ കെ) 2016-09-25 20:32:32 +05:30
parent 1d5a05d112
commit 3bf5813096
97 changed files with 115 additions and 116 deletions

View file

@ -272,7 +272,7 @@ is called, the two conditions above apply like normal.
Dedicated and shared workers don't have an event that corresponds to the `load`
event in a document. Therefore these worker tests always behave as if the
`explicit_done` property is set to true. Service workers depend on the
[install](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#service-worker-global-scope-install-event)
[install](https://w3c.github.io/ServiceWorker/index.html#service-worker-global-scope-install-event)
event which is fired following the completion of [running the
worker](https://html.spec.whatwg.org/multipage/workers.html#run-a-worker).
@ -374,7 +374,7 @@ object. These objects are structures as follows:
The `testharness.js` script can be used from within [dedicated workers, shared
workers](https://html.spec.whatwg.org/multipage/workers.html) and [service
workers](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/).
workers](https://w3c.github.io/ServiceWorker/).
Testing from a worker script is different from testing from an HTML document in
several ways:
@ -401,7 +401,7 @@ several ways:
complete](#determining-when-all-tests-are-complete)). So these worker tests
behave as if they were started with the `explicit_done` option. Service
workers depend on the
[oninstall](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#service-worker-global-scope-install-event)
[oninstall](https://w3c.github.io/ServiceWorker/index.html#service-worker-global-scope-install-event)
event and don't require an explicit `done` call.
Here's an example that uses a dedicated worker.
@ -434,7 +434,7 @@ Here's an example that uses a dedicated worker.
The argument to the `fetch_tests_from_worker` function can be a
[`Worker`](https://html.spec.whatwg.org/multipage/workers.html#dedicated-workers-and-the-worker-interface),
a [`SharedWorker`](https://html.spec.whatwg.org/multipage/workers.html#shared-workers-and-the-sharedworker-interface)
or a [`ServiceWorker`](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#service-worker-obj).
or a [`ServiceWorker`](https://w3c.github.io/ServiceWorker/#service-worker-obj).
Once called, the containing document fetches all the tests from the worker and
behaves as if those tests were running in the containing document itself.

View file

@ -2,14 +2,14 @@ interface Foo {
Promise<ResponsePromise<sequence<DOMString?>>> bar();
};
// Extracted from https://slightlyoff.github.io/ServiceWorker/spec/service_worker/ on 2014-05-08
// Extracted from https://w3c.github.io/ServiceWorker/ on 2014-05-08
interface ServiceWorkerClients {
Promise<Client[]?> getServiced();
Promise<any> reloadAll();
};
// Extracted from https://slightlyoff.github.io/ServiceWorker/spec/service_worker/ on 2014-05-13
// Extracted from https://w3c.github.io/ServiceWorker/ on 2014-05-13
interface FetchEvent : Event {
ResponsePromise<any> default();

View file

@ -1,4 +1,4 @@
// Extracted from https://slightlyoff.github.io/ServiceWorker/spec/service_worker/ on 2014-05-06
// Extracted from https://w3c.github.io/ServiceWorker/ on 2014-05-06
[MapClass(DOMString, DOMString)]
interface HeaderMap {