Open
Bug 1273319
Opened 9 years ago
Updated 3 years ago
Update addIceCandidate() to accept null candidate
Categories
(Core :: WebRTC: Signaling, defect, P3)
Core
WebRTC: Signaling
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
| backlog | webrtc/webaudio+ |
People
(Reporter: drno, Unassigned)
Details
The latest editor draft specifies that addIceCandidate() needs to return a Promise and also accept the empty end-of-candidates argument. We should update our implementation accordingly.
|
Reporter | |
Updated•9 years ago
|
backlog: --- → webrtc/webaudio+
Rank: 25
|
||
Comment 1•9 years ago
|
||
addIceCandidate() has returned a promise since 37 (bug 1091898), so this is just about the null candidate.
Summary: Update addIceCandidate() to return promise and accept EOC → Update addIceCandidate() to accept null candidate
|
|
||
Comment 2•9 years ago
|
||
We may want to wait until https://github.com/webrtc/adapter/pull/294#issuecomment-219580054 resolves.
|
|
||
Comment 3•9 years ago
|
||
The issue to follow here is https://github.com/rtcweb-wg/jsep/issues/251#issuecomment-195171292
|
|
||
Comment 4•9 years ago
|
||
Whenever we fix this, we should update our synchronous input validation code to match the spec at the same time, and throw TypeError.
|
||
Comment 5•8 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•