Open
Bug 1095226
Opened 10 years ago
Updated 2 years ago
[meta] Validate that no unsupported changes have been made on SDP passed to SetLocal/Remote
Categories
(Core :: WebRTC: Signaling, defect, P3)
Core
WebRTC: Signaling
Tracking
()
NEW
People
(Reporter: bwc, Unassigned)
References
Details
(Keywords: meta)
No description provided.
Reporter | ||
Updated•9 years ago
|
Summary: Validate that no unsupported changes have been made on SDP passed to SetLocal/Remote → [meta] Validate that no unsupported changes have been made on SDP passed to SetLocal/Remote
Comment 2•9 years ago
|
||
I'm giving this a priority so we can do a bug breakdown.
Byron -- would it be reasonable (time-wise) for you to do a bug breakdown on this between now and the end of this month (November)? Or are you too swamped?
Comment 3•9 years ago
|
||
One issue that came up recently when abr was helping a developer: The dev made changes to the SDP that we chose not to act on, but we currently fail silently instead of making setLocalDescription fail. That would be a good first bug to file (blocking this bug) and fix.
Reporter | ||
Comment 4•9 years ago
|
||
We have a partial breakdown in the code over here: https://dxr.mozilla.org/mozilla-central/source/media/webrtc/signaling/src/jsep/JsepSessionImpl.cpp?case=true&from=JsepSessionImpl.cpp#1773
Some time/thought needs to be put into this. I suspect simulcast is going to keep me pretty busy.
Flags: needinfo?(docfaraday)
Comment 5•9 years ago
|
||
Given our other priorities, I need to lower this slightly (to a high P2).
Rank: 19 → 21
Priority: P1 → P2
Comment 6•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•