W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2017

Re: [webrtc-pc] Candidate from onicecandidate event and addIceCandidate are incompatible

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Mar 2017 05:03:49 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-288299496-1490159027-sysbot+gh@w3.org>
> However, having said that, non-Trickle-ICE implementations can still get the same information by waiting until end-of-candidate has been received for all media streams (although that's a little bit more complicated) - is that correct?

Yes. Though they don't even have to do that, they can just wait for the gathering state to change to "complete".

> Is this referring to the candidate argument or the member?

The whole "if candidate is not null" part can be removed, this is left over from the previous approach.

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1077#issuecomment-288299496 using your GitHub account
Received on Wednesday, 22 March 2017 05:03:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:14:52 UTC