Re: [webrtc-pc] addIceCandidate end of candidates woes

> There are three things that come out of the icecandidate event

I am confused now. Is there any place in the spec where the second case of empty string candidate must be fired? Chrome and Firefox currently only fire case 1 and 3.

The spec need to clarify the sequence of events expected to be fired. And if null candidate is there for legacy reason and listening to `icegatheringstatechange` is the better approach, there should be a note to recommend so.

Even the example 13 in section 11.2 of the spec do not consider the case for null candidate.

-- 
GitHub Notification of comment by soareschen
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1213#issuecomment-301974938 using your GitHub account

Received on Wednesday, 17 May 2017 03:25:25 UTC