RTCPeerConnection.onicecandidateerror

Category: WebRTC
Type: New or changed feature
Status: Enabled by default (Chrome 77)
Intent stage: Prepare to ship

Breaking change: No
Enterprise impact: None
Spec maturity: Incubation
Web Platform Tests: Yes

WPT details: Configure PC with bogus TURN server, trigger ICE gathering, and expect PeerConnection::icecandidateerror event to fire with all properties populated.

Summary

Adds the incecandidateerror event which provides detailed information about WebRTC ICE candidate gathering failures, including the ones defined by STUN (RFC5389) and TURN (RFC5766).

Motivation

Diagnosing ICE connectivity issues without having access to detailed gathering failures can be a challenge. Support for ICE candidate errors is targeted towards better connectivity troubleshooting and network diagnostics.

Standards & signals

Specification: https://www.w3.org/TR/webrtc/#dom-rtcpeerconnectioniceerrorevent
Firefox: No signal
Safari: No signal
Web developers: No signals
Tracking bug: https://bugs.chromium.org/p/webrtc/issues/detail?id=3098

Ecosystem

Web Platform Tests: https://wpt.fyi/results/?q=rtcpeerconnection-onicecandidateerror
Chrome Platform Showcase: https://chrome-platform-showcase.paulkinlan-ea.deno.net/features
GenDN reference: https://gendn.paulkinlan-ea.deno.net/features
chrome.dev demos search: https://www.google.com/search?q=site%3Achrome.dev+RTCPeerConnection.onicecandidateerror
MDN Web Docs: https://developer.mozilla.org/en-US/search?q=RTCPeerConnection.onicecandidateerror
Baseline status: https://webstatus.dev/?q=RTCPeerConnection.onicecandidateerror

Docs: https://www.w3.org/TR/webrtc/#dom-rtcpeerconnectioniceerrorevent

View on chromestatus.com