| OLD | NEW |
|---|
| (Empty) | |
| 1 <!DOCTYPE html> |
| 2 <html> |
| 3 <title>Service Workers: event.respondWith(r)</title> |
| 4 <head> |
| 5 <link rel="help" href="https://w3c.github.io/ServiceWorker/#respond-with
-method"> |
| 6 <script src="/resources/testharness.js"></script> |
| 7 <script src="/resources/testharnessreport.js"></script> |
| 8 |
| 9 </head> |
| 10 <body> |
| 11 |
| 12 <!-- |
| 13 |
| 14 `event.respondWith(r)` method must run the steps, from step 10 to step 15, |
| 15 defined in the [_OnFetchRequest algorithm][1]. |
| 16 |
| 17 The `r` argument must resolve with a [AbstractResponse][2], else a |
| 18 [NetworkError][3] is thrown. If the request is a top-level navigation and the |
| 19 return value is a [OpaqueResponse][4] (an opaque response body), a |
| 20 [NetworkError][3] is thrown. The final URL of all successful (non |
| 21 network-error) responses is the [requested][5] URL. Renderer-side security |
| 22 checks about tainting for cross-origin content are tied to the transparency (or |
| 23 opacity) of the [Response][6] body, not URLs. |
| 24 |
| 25 |
| 26 |
| 27 [1]: #on-fetch-request-algorithm |
| 28 [2]: #abstract-response-interface |
| 29 [3]: http://w3c.github.io/dom/#networkerror |
| 30 [4]: #opaque-response-interface |
| 31 [5]: #request-objects |
| 32 [6]: #response-interface |
| 33 |
| 34 --> |
| 35 |
| 36 |
| 37 |
| 38 <script> |
| 39 test(function() { |
| 40 // not_implemented(); |
| 41 }, "There are no tests for section event.respondWith(r) so far."); |
| 42 </script> |
| 43 |
| 44 </body> |
| 45 </html> |
| 46 |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2415873002:
Import w3c tests for the service workers (Closed)
