26644 2014-08-22 21:28:51 +0000 MID in Candidate event attributes 2014-12-15 10:39:37 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified All All RESOLVED LATER P2 normal --- 1 martin.thomson martin.thomson harald juberti public-webrtc oldest_to_newest 110491 0 martin.thomson 2014-08-22 21:28:51 +0000 http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtcicecandidate-type It's not clear what the browser's obligations are with respect to sdpMid and sdpMLineIndex. There is an "If present" attached to sdpMid, which might imply something. I think that we should always, always include both in events. And we should require that input include one or other. (And we should work out which takes precedence, or surface an error if both are present.) Did we agree to remove the whole null candidate thing by surfacing an ICE state change? 110965 1 juberti 2014-09-04 00:49:24 +0000 We did agree to surface an ICE state change. I think we need to keep onicecandidate(null) for backcompat though. 114386 2 juberti 2014-10-31 18:15:18 +0000 Plan is to make a PR to add onicegatheringstatechange and leave onicecandidate(null) 114396 3 harald 2014-10-31 18:31:14 +0000 WebRTC implementations will always generate MID. (if the JSEP docs don't already say so, they should be fixed.) There should be a separate bug for the icegatheringstatechange event. 114526 4 martin.thomson 2014-11-04 23:11:29 +0000 https://github.com/w3c/webrtc-pc/pull/27 As it turns out onicecandidate(null) wasn't documented, or even permitted. 116323 5 dom 2014-12-15 10:39:37 +0000 WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues Please subscribe to the issues you want to keep watching.