summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html
diff options
context:
space:
mode:
Diffstat (limited to 'testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html')
-rw-r--r--testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html38
1 files changed, 38 insertions, 0 deletions
diff --git a/testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html b/testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html
new file mode 100644
index 000000000..6981d3079
--- /dev/null
+++ b/testing/web-platform/tests/service-workers/stub-4.7.2.2-replace-method.html
@@ -0,0 +1,38 @@
+<!DOCTYPE html>
+<html>
+<title>Service Workers: event.replace()</title>
+ <head>
+ <link rel="help" href="https://w3c.github.io/ServiceWorker/#replace-method">
+ <script src="/resources/testharness.js"></script>
+ <script src="/resources/testharnessreport.js"></script>
+
+ </head>
+ <body>
+
+<!--
+
+`replace()` interacts with `waitUntil` method in the following way:
+
+- Successful installation can be delayed by `waitUntil`, perhaps by
+ subsequent event handlers.
+- Replacement only happens upon successful installation
+- Therefore, replacement of the [active worker][1] (if any) is not
+ immediate, however it may occur as soon as the end of the current turn.
+
+
+
+[1]: #navigator-service-worker-active
+
+-->
+
+
+
+ <script>
+ test(function() {
+ // not_implemented();
+ }, "There are no tests for section event.replace() so far.");
+ </script>
+
+ </body>
+</html>
+