| Andrew Top | 61a8495 | 2019-04-30 15:07:33 -0700 | [diff] [blame^] | 1 | <!DOCTYPE html> |
| 2 | <html> |
| 3 | <title>Service Workers: event.waitUntil(f)</title> |
| 4 | <head> |
| 5 | <link rel="help" href="https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#wait-until-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.waitUntil(f)` method, when called in `oninstall` or `onactivate`, |
| 15 | extends the lifetime of the event. When called in `oninstall`, it delays |
| 16 | treating the installing worker until the passed [Promise][1] resolves |
| 17 | successfully. This is primarily used to ensure that a `ServiceWorker` is not |
| 18 | active until all of the core caches it depends on are populated. When called in |
| 19 | `onactivate`, it delays treating the activating worker until the passed |
| 20 | [Promise][1] resolves successfully. This is primarily used to ensure that any |
| 21 | [Functional events][2] are not dispatched to the `ServiceWorker` until it |
| 22 | upgrades database schemas and deletes the outdated cache entries. |
| 23 | |
| 24 | [1]: http://goo.gl/3TobQS |
| 25 | [2]: #functional-events |
| 26 | |
| 27 | --> |
| 28 | |
| 29 | |
| 30 | |
| 31 | <script> |
| 32 | test(function() { |
| 33 | // not_implemented(); |
| 34 | }, "There are no tests for section event.waitUntil(f) so far."); |
| 35 | </script> |
| 36 | |
| 37 | </body> |
| 38 | </html> |
| 39 | |
