This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The RTCPeerConnectionIceEvent interface represents events that occurs in relation to ICE candidates with the target, usually an RTCPeerConnection. Only one event is of this type: icecandidate.
A RTCPeerConnectionIceEvent being an Event, this event also implements these properties.
RTCPeerConnectionIceEvent.candidate Read only
RTCIceCandidate containing the candidate associated with the event.RTCPeerConnectionIceEvent()DOMString representing the type of the event; the second a dictionary containing the RTCIceCandidate it refers to.A RTCPeerConnectionIceEvent being an Event, this event also implements these properties. There is no specific RTCDataChannelEvent method.
pc.onicecandidate = function( ev ) {
alert("The ICE candidate (transport address: '" +
ev.candidate.candidate +
"') has been added to this connection.");
}
| Specification | Status | Comment |
|---|---|---|
| WebRTC 1.0: Real-time Communication Between Browsers The definition of 'RTCPeerConnectionIceEvent' in that specification. | Working Draft | Initial definition. |
| Feature | Chrome | Edge | Firefox (Gecko) | Internet Explorer | Opera | Safari |
|---|---|---|---|---|---|---|
| Basic support | (Yes)[1] | (Yes) | (Yes) | No support | (Yes) | ? |
| Feature | Android Webview | Chrome for Android | Edge | Firefox Mobile (Gecko) | IE Mobile | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|---|---|
| Basic support | (Yes)[1] | (Yes)[1] | (Yes) | ? | No support | ? | ? |
[1] Before Chrome 56, this was implemented as RTCIceCandidateEvent.
RTCPeerConnection.
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnectionIceEvent