- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Wed, 24 Apr 2013 07:08:18 +0200
- To: cowwoc <cowwoc@bbs.darktech.org>
- CC: public-webrtc@w3.org
On 2013-04-23 19:26, cowwoc wrote: > On 23/04/2013 12:20 PM, Iñaki Baz Castillo wrote: >> 2013/4/23 Adam Bergkvist <adam.bergkvist@ericsson.com>: >>> On 2013-04-22 16:26, Tommy Widenflycht (ᛏᚮᛘᛘᚤ) wrote: >>>> Chromium sends the null icecandidate just because there isn't a >>>> onicegatheringcomplete event handler. >>> >>> That's the correct behavior according to the spec. >> >> Which behavior? Could you please point to the exact line/section in >> the spec about that? >> >> Thanks a lot. >> >> >> -- >> Iñaki Baz Castillo >> <ibc@aliax.net> >> > > Haha :) I'm pretty sure I filed a bug report specifically about > this issue. The current behavior is *not* documented in the spec the > last time I checked. Hi It's rather new. The text was added in the release about a month ago. In the "Operation" subsection of the "Peer-to-peer connections" section [1]. "When the ICE Agent needs to notify the script about the candidate gathering progress, the user agent must queue a task to run the following steps:" ... "3. If the intent of the ICE Agent is to notify the script that:" ... " * The gathering process is done. Set connection's ice gathering state to completed and let newCandidate be null. 4. Fire a icecandidate event named icecandidate with newCandidate at connection." /Adam [1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#operation
Received on Wednesday, 24 April 2013 05:08:42 UTC