Accept candidate messages that are zero numbered

RESOLVED FIXED in mozilla20

Status

()

defect
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: ekr, Assigned: jib)

Tracking

unspecified
mozilla20
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [WebRTC],[blocking-webrtc-interop],[blocking-webrtc+][qa-])

Attachments

(1 attachment, 1 obsolete attachment)

Reporter

Description

7 years ago
No description provided.
Reporter

Comment 2

7 years ago
http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtcicecandidate-type

Requires that candidates are 0-based indexed. We use 1-based indexing internally for m-lines.
This should be fixed in the JS.

Here is a prototype patch that needs to be cleaned-up and landed.
Reporter

Updated

7 years ago
Whiteboard: [WebRTC],[blocking-webrtc-interop]
Assignee: ekr → jib
Attachment #687554 - Attachment is obsolete: true
Whiteboard: [WebRTC],[blocking-webrtc-interop] → [WebRTC],[blocking-webrtc-interop],[blocking-webrtc+]
Attachment #692999 - Flags: review?(rjesup)
Attachment #692999 - Flags: review?(rjesup) → review+
Attachment #692999 - Flags: checkin?(rjesup)
Attachment #692999 - Flags: checkin?(rjesup) → checkin+
https://hg.mozilla.org/mozilla-central/rev/08e0e0862006
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Whiteboard: [WebRTC],[blocking-webrtc-interop],[blocking-webrtc+] → [WebRTC],[blocking-webrtc-interop],[blocking-webrtc+][qa-]
You need to log in before you can comment on or make changes to this bug.