summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/service-workers/stub-4.5.4-opaque-response.html
diff options
context:
space:
mode:
Diffstat (limited to 'testing/web-platform/tests/service-workers/stub-4.5.4-opaque-response.html')
-rw-r--r--testing/web-platform/tests/service-workers/stub-4.5.4-opaque-response.html36
1 files changed, 36 insertions, 0 deletions
diff --git a/testing/web-platform/tests/service-workers/stub-4.5.4-opaque-response.html b/testing/web-platform/tests/service-workers/stub-4.5.4-opaque-response.html
new file mode 100644
index 000000000..a91306f4c
--- /dev/null
+++ b/testing/web-platform/tests/service-workers/stub-4.5.4-opaque-response.html
@@ -0,0 +1,36 @@
+<!DOCTYPE html>
+<html>
+<title>Service Workers: OpaqueResponse</title>
+ <head>
+ <link rel="help" href="https://w3c.github.io/ServiceWorker/#opaque-response">
+ <script src="/resources/testharness.js"></script>
+ <script src="/resources/testharnessreport.js"></script>
+
+ </head>
+ <body>
+
+<!--
+
+`OpaqueResponse` objects are immutable but constructable. The `fetch()` API
+returns this type for cross-origin responses.
+
+Their role is to encapsulate the security properties of the web platform. As
+such, their `body` attribute will always be `undefined` and the list of
+readable `headers` is heavily filtered.
+
+`OpaqueResponse` objects may be forwarded on to rendering documents in exactly
+the same way as mutable `Response` objects.
+
+-->
+
+
+
+ <script>
+ test(function() {
+ // not_implemented();
+ }, "There are no tests for section OpaqueResponse so far.");
+ </script>
+
+ </body>
+</html>
+