Re: [webrtc-pc] RTCIceCandidate: component attribute missing?

Perhaps the reason it was left out is because we have `RTCIceTransport.component`:

So all candidates returned by `RTCIceTransport.getLocalCandidates()` have a component of `RTCIceTransport.component`.  

While in WebRTC we also have `RTCIceTransport.component`, there is no `RTCIceTransport.onicecandidate` EventHandler, only `RTCPeerConnection.onicecandidate`. Since in WebRTC `RTCIceTransport` objects do not necessarily have a unique `ufrag`, you can't use `RTCIceCandidate.ufrag` to determine the related `RTCIceTransport` object.

GitHub Notification of comment by aboba
Please view or discuss this issue at using your GitHub account

Received on Monday, 8 May 2017 20:25:34 UTC