RTCPeerConnection: signalingstatechange event
BaselineWidely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since September 2017.
Asignalingstatechange event is sent to anRTCPeerConnection to notify it that its signaling state, as indicated by thesignalingState property, has changed.
This event is not cancelable and does not bubble.
Syntax
Use the event name in methods likeaddEventListener(), or set an event handler property.
js
addEventListener("signalingstatechange", (event) => { })onsignalingstatechange = (event) => { }Event type
A genericEvent.
Examples
Given anRTCPeerConnection,pc, and anupdateStatus() function that presents status information to the user, this code sets up an event handler to let the user know when the ICE negotiation process finishes up.
js
pc.addEventListener( "signalingstatechange", (ev) => { switch (pc.signalingState) { case "stable": updateStatus("ICE negotiation complete"); break; } }, false,);Usingonsignalingstatechange, it looks like this:
js
pc.onsignalingstatechange = (ev) => { switch (pc.signalingState) { case "stable": updateStatus("ICE negotiation complete"); break; }};Specifications
| Specification |
|---|
| WebRTC: Real-Time Communication in Browsers # event-signalingstatechange |