We're looking for a person or people to help audit MDN to find places we could speed up. Is this you or someone you know? Check out the RFP: https://mzl.la/2IHcMiE


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
Contains the RTCIceCandidate containing the candidate associated with the event.


Returns a new RTCPeerConnectionIceEvent. It takes two parameters, the first being a 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 propertiesThere 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.
Candidate Recommendation Initial definition.

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support

Yes — 561


Yes Yes ? Yes ?
candidate56 Yes Yes ? Yes ?
RTCPeerConnectionIceEvent() constructor.56 Yes Yes ? Yes ?
FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support

Yes — 561


Yes — 561


? Yes Yes ? ?
candidate5656 ? Yes Yes ? ?
RTCPeerConnectionIceEvent() constructor.5656 ? Yes Yes ? ?

1. Supported as RTCIceCandidateEvent.

See also

Document Tags and Contributors

 Contributors to this page: fscholz, jpmedley, abbycar, teoli
 Last updated by: fscholz,