- From: Dennis Boldt via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Aug 2018 14:53:02 +0000
- To: public-webrtc-logs@w3.org
@aboba An example will clarify how to do the end-of-candidates. @jan-ivar Why is it example (2)? Reading the spec tells me `Promise<void> addIceCandidate((RTCIceCandidateInit or RTCIceCandidate) candidate);`, which yields to my example (4) - or do I miss something? Also [developer.mozilla.org](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/addIceCandidate#Example) tells me to use `new RTCIceCandidate(...)`. @alvestrand Thanks for the response with the Chrome bug. To give you a context: In my applitcation I signal offer, answer and ICE candidates. The `PeerConnection.iceConnectionState` for the answerer (callee) is `new`, `checking` and `connected`, but it never reaches the `completed` state. I assume, its required to inform the callee about the end-of-candidates to get in the final state. -- GitHub Notification of comment by boldt Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1952#issuecomment-409954860 using your GitHub account
Received on Thursday, 2 August 2018 14:53:37 UTC