Why does Chrome fires onicecandidate() with candidate=null ?

[Iñaki Baz Castillo]

Chrome 25, 26 fires onicecandidate(e) with e.candidate=null when there
are no more ICE candidates. This is not part of the standard at all:

http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCPeerConnection-onicecandidate
----------------------------------
onicecandidate of type EventHandler

This event handler, of event handler event type icecandidate, must be
supported by all objects implementing the RTCPeerConnection interface.
It is called any time there is a new ICE candidate added to a previous
offer or answer.
----------------------------------

There are other ICE related events not yet documented like
ongatheringchange() and onicechange() that "may" will be fired with
some kind of argument when there are no more ICE candidates.

Does somebody know about it?

Thanks a lot.


--
Iñaki Baz Castillo
<i...@aliax.net>

[Justin Uberti]

This is a spec issue (see http://lists.w3.org/Archives/Public/public-webrtc/2013Feb/0052.html); it is in the process of being corrected.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Iñaki Baz Castillo]

2013/3/6 Justin Uberti <jub...@google.com>:

> This is a spec issue (see
> http://lists.w3.org/Archives/Public/public-webrtc/2013Feb/0052.html); it is
> in the process of being corrected.