messageerror
event is fired on a
MessagePort
object when it receives a message that can't be deserialized.
| 冒泡 | No |
|---|---|
| 可取消 | No |
| 接口 |
MessageEvent
|
| 事件处理程序特性 |
onmessageerror
|
Suppose a script creates a
MessageChannel
and sends one of the ports to a different browsing context, such as another
<iframe>
, using code like this:
const channel = new MessageChannel();
const myPort = channel.port1;
const targetFrame = window.top.frames[1];
const targetOrigin = 'https://example.org';
const messageControl = document.querySelector('#message');
const channelMessageButton = document.querySelector('#channel-message');
channelMessageButton.addEventListener('click', () => {
myPort.postMessage(messageControl.value);
})
targetFrame.postMessage('init', targetOrigin, [channel.port2]);
The target can receive the port and start listening for messages and message errors on it using code like this:
window.addEventListener('message', (event) => {
const myPort = event.ports[0];
myPort.addEventListener('message', (event) => {
received.textContent = event.data;
});
myPort.addEventListener('messageerror', (event) => {
console.error(event.data);
});
myPort.start();
});
Note that the listener must call
MessagePort.start()
before any messages will be delivered to this port. This is only needed when using the
addEventListener()
method: if the receiver uses
onmessage
instead,
start()
is called implicitly:
window.addEventListener('message', (event) => {
const myPort = event.ports[0];
myPort.onmessage = (event) => {
received.textContent = event.data;
};
myPort.onmessageerror = (event) => {
console.error(event.data);
};
});
| 规范 | 状态 |
|---|---|
| HTML 实时标准 | 实时标准 |
| 桌面 | 移动 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
messageerror
event
|
Chrome 60 | Edge 18 | Firefox 57 | IE ? | Opera 47 | Safari ? | WebView Android 60 | Chrome Android 60 | Firefox Android 57 | Opera Android 47 | Safari iOS ? | Samsung Internet Android 8.0 |
完整支持
兼容性未知
message
.
MessagePort
message
messageerror