Closed
Bug 1115703
Opened 10 years ago
Closed 9 years ago
onicecandidate event must set candidate.sdpMid
Categories
(Core :: WebRTC, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1192813
mozilla39
backlog | webrtc/webaudio+ |
People
(Reporter: ibc, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Steps to reproduce:
Create a mozRTCPeerConnection and log the data provided by onicecandidate event.
Actual results:
The candidate.sdpMid field has an empty string as value.
Expected results:
According to the WebRTC draft the event.candidate object must include:
-------------------
interface RTCIceCandidate {
attribute DOMString? candidate;
attribute DOMString? sdpMid;
attribute unsigned short? sdpMLineIndex;
serializer = {attribute};
};
sdpMid of type DOMString, , nullable
If present, this contains the identifier of the "media stream identification" as defined in [RFC3388] for the m-line this candidate is associated with.
------------------
Firefox (at least version Nightly 37) does include a "a:mid" attribute in every m= section of the SDP:
-----------------
m=audio 9 RTP/SAVPF 109 9 0 8
c=IN IP4 0.0.0.0
a=mid:sdparta_0
-----------------
and thus it should set the candidate.sdpMid field with "sdparta_0".
Comment 1•10 years ago
|
||
Bryon? If this is right, can you confirm and set pri/rank/Blocking? Thanks!
Flags: needinfo?(docfaraday)
Comment 2•10 years ago
|
||
Yes, this is right. While it is a spec compliance problem, it isn't causing interop problems because the same spec requires addIceCandidate to handle our (incorrect) behavior. Still would be good to get this fixed.
backlog: --- → webRTC+
Rank: 30
Flags: needinfo?(docfaraday)
Priority: -- → P3
Comment 4•10 years ago
|
||
When we can fit it in, yes.
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•9 years ago
|
||
Looks to me like this got fixed at some point. I see in Fx 46 ICE candidates have Mid attributes set.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 6•9 years ago
|
||
For the record: got fixed in 39 through bug 1192813.
Resolution: FIXED → DUPLICATE
Target Milestone: --- → mozilla39
You need to log in
before you can comment on or make changes to this bug.
Description
•