WebSocket: message event
Baseline Widely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015.
Note: This feature is available inWeb Workers.
Themessage event is fired when data is received through aWebSocket.
In this article
Syntax
Use the event name in methods likeaddEventListener(), or set an event handler property.
addEventListener("message", (event) => { })onmessage = (event) => { }Event type
AMessageEvent. Inherits fromEvent.
Event properties
In addition to the properties listed below, properties from the parent interface,Event, are available.
dataRead onlyThe data sent by the message emitter. The type of this property depends on the type of the WebSocket message and the value of
WebSocket.binaryType.- If the message type is "text", then this field is a string.
- If the message type is "binary" type, then the type of this property can be inferred from the
binaryTypeof this socket:ArrayBufferifbinaryTypeis"arraybuffer",BlobifbinaryTypeis"blob". This does not have an associated media type (Blob.typeis"").
originRead onlyA string representing the origin of the message emitter.
Other properties from theMessageEvent interface are present, but do not pertain to the WebSocket API and are left at their default values:
lastEventIdRead onlysourceRead onlyportsRead only
Examples
// Create WebSocket connection.const socket = new WebSocket("ws://localhost:8080");// Listen for messagessocket.addEventListener("message", (event) => { console.log("Message from server ", event.data);});Specifications
| Specification |
|---|
| WebSockets> # dom-websocket-onmessage> |