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, 15 Mar 2017 20:46:35 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-286873650-1489610794-sysbot+gh@w3.org>
> First of all, do you mean the member candidate can be empty string 

The member. See section 5.6 for when the corresponding "icecandidate" event is fired. I agree it needs to be clarified.

> Please also state what should happen in case the argument candidate is null.

As I recall, the working group decided we didn't need to worry about this because this was only briefly allowed by the specification and no one implemented it.

> I would expect the candidate attribute to always contain an RTCIceCandidate which cannot be null

The working group decided to keep this special "all gathering is done" `null` candidate for backwards compatibility; apps that communicate with an endpoint that doesn't do trickle ICE rely on it (probably because Chrome didn't implement the "gatheringstatechange" event until just recently).

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1077#issuecomment-286873650 using your GitHub account
Received on Wednesday, 15 March 2017 20:46:42 UTC

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