- From: <bugzilla@jessica.w3.org>
- Date: Fri, 22 Aug 2014 21:28:51 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26644 Bug ID: 26644 Summary: Candidate event attributes Product: WebRTC Working Group Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: WebRTC API Assignee: public-webrtc@w3.org Reporter: martin.thomson@gmail.com CC: public-webrtc@w3.org 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? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Friday, 22 August 2014 21:28:53 UTC