Revision 6668ff3716086d3f8efead0f5db2d8d2864c3563 authored by Robert Ma on 21 March 2018, 17:35:46 UTC, committed by Robert Ma on 21 March 2018, 17:35:46 UTC
1. Check the HTTP port of wptserve instead of HTTPS to avoid the unnecessary complexities of setting up SSL context (which may fail in some environments). 2. Use exponential backoff when waiting for wptserve and specify a maximum retry to avoid indefinite hang. 3. Use `terminate` instead of `kill` to give wptserve a chance to clean up, which is especially useful when running locally.
1 parent dbb38a6
stub-3.2.10-navigator-service-worker-oncontrollerchange.html
<!DOCTYPE html>
<html>
<title>Service Workers: oncontrollerchange</title>
<head>
<link rel="help" href="https://w3c.github.io/ServiceWorker/#navigator-service-worker-oncontrollerchange">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
</head>
<body>
<!--
`navigator.serviceWorker.oncontrollerchange` is the [event handler][1] that
must be supported as attribute by the `[ServiceWorkerContainer][2]` object. A
`controllerchange` event using the `[Event][3]` interface is dispatched on
`[ServiceWorkerContainer][2]` object (See step 7 of the [_Activation
algorithm][4]) when the associated Service Worker [registration][5] for the
document enters the [activation process][6]. When the [activation process][6]
is triggered by `replace()` method call within the event handler of the
`install` event, `navigator.serviceWorker.controller` immediately reflects the
[active worker][7] as the Service Worker that [controls][8] the document.
[1]: http://goo.gl/rBfiz0
[2]: #service-worker-container-interface
[3]: http://goo.gl/Mzv7Dv
[4]: #activation-algorithm
[5]: #registration
[6]: #activation-process
[7]: #active-worker
[8]: #document-control
-->
<script>
test(function() {
// not_implemented();
}, "There are no tests for section oncontrollerchange so far.");
</script>
</body>
</html>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...