OLD | NEW |
(Empty) | |
| 1 <!DOCTYPE html> |
| 2 <html> |
| 3 <title>Service Workers: onmessage</title> |
| 4 <head> |
| 5 <link rel="help" href="https://w3c.github.io/ServiceWorker/#service-work
er-global-scope-onmessage"> |
| 6 <script src="/resources/testharness.js"></script> |
| 7 <script src="/resources/testharnessreport.js"></script> |
| 8 |
| 9 </head> |
| 10 <body> |
| 11 |
| 12 <!-- |
| 13 |
| 14 `self.onmessage` is the [event handler][1] that must be supported as attribute |
| 15 by the `ServiceWorkerGlobalScope` object. `ServiceWorkerGlobalScope` objects |
| 16 act as if they had an implicit `[MessagePort][2]` associated with them. This |
| 17 port is part of a channel that is set up when the worker is created, but it is |
| 18 not exposed. This object must never be garbage collected before the |
| 19 `ServiceWorkerGlobalScope` object. |
| 20 |
| 21 All messages received by that port must immediately be retargeted at the |
| 22 `ServiceWorkerGlobalScope` object. That is, an event named `message` using the |
| 23 `[MessageEvent][3]` interface is dispatched on ServiceWorkerGlobalScope object. |
| 24 The `event.source` of these `[MessageEvent][3]`s are instances of `[Client][4]`. |
| 25 |
| 26 |
| 27 |
| 28 [1]: http://goo.gl/rBfiz0 |
| 29 [2]: http://goo.gl/tHBrI6 |
| 30 [3]: http://goo.gl/S5e0b6 |
| 31 [4]: #client-interface |
| 32 |
| 33 --> |
| 34 |
| 35 |
| 36 |
| 37 <script> |
| 38 test(function() { |
| 39 // not_implemented(); |
| 40 }, "There are no tests for section onmessage so far."); |
| 41 </script> |
| 42 |
| 43 </body> |
| 44 </html> |
| 45 |
OLD | NEW |