RTCPeerConnection.onicecandidateerror event changes

Category: WebRTC
Type: New or changed feature
Status: Enabled by default (Chrome 81)
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

Replaces hostCandidate with explicit address and port for oncecandidateerror event according to the latest WebRTC 1.0 spec - https://github.com/w3c/webrtc-pc/pull/2322/

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/chromium/issues/detail?id=1013564

Ecosystem

Web Platform Tests: https://wpt.fyi/results/?q=rtcpeerconnection-onicecandidateerror-event-changes
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%20event%20changes
MDN Web Docs: https://developer.mozilla.org/en-US/search?q=RTCPeerConnection.onicecandidateerror%20event%20changes
Baseline status: https://webstatus.dev/?q=RTCPeerConnection.onicecandidateerror%20event%20changes

View on chromestatus.com