Intent to Implement: Rename RTCIceCandidateEvent to RTCPeerConnectionIceEvent and expose

[Luna]

Summary This entry track renaming RTCIceCandidateEvent (implemented and shipped) to RTCPeerConnectionIceEvent and exposing RTCPeerConnectionIceEvent constructor.

Spec https://w3c.github.io/webrtc-pc/#rtcpeerconnectioniceevent

Interoperability risk Firefox: Shipped Edge: No public signals Safari: No public signals Web developers: No signals

OWP launch tracking bug https://crbug.com/659286

Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5685429277818880

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes

[Philip Jägenstedt]

Changing title to "Intent to Ship" to reflect that this won't happen behind a flag. Will also update https://bit.ly/blinkintents.

This is also a change I suggested after looking at window.*RTC* in various browsers, but again I think it's trivial so LGTM1.

[Rick Byers]

So the compat risk is basically zero because RTCIceCandidateEvent was [NoInterfaceObject] and there's no reason to think anyone is using feature detection of window.RTCPeerConnectionIceEvent, right?

LGTM2

[Philip Jägenstedt]

That's right. When exposing new interfaces we typically don't expect any compat fallout, but I took a quick look at "RTCPeerConnectionIceEvent" in httparchive, only 9 hits. All except one in lists of interfaces, and one was feature detection for WebRTC:

if ("RTCIceCandidate" in window || "RTCPeerConnectionIceEvent" in window) { ... }

Since RTCIceCandidate is already exposed, nothing will change.

[TAMURA, Kent]

LGTM3.

--

TAMURA Kent
Software Engineer, Google