Closed Bug 844295 Opened 11 years ago Closed 11 years ago

Unexpose the removeStream function on the Peer Connection object temporarily

Categories

(Core :: WebRTC, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla22

People

(Reporter: jsmith, Assigned: snandaku)

Details

(Whiteboard: [webrtc][blocking-webrtc+][qa-])

Attachments

(1 file)

The removeStream function right now doesn't have much use without renegotiation existing and fixing associated bugs like bug 842455. So exposing this function publicly right now really introduces a developer footgun - they are using a function that doesn't have much use and known problems with it. We might want to turn the API off temporarily until we solve the underlying issues.
Any objections to a small patch to do this for now, if it's useless/unsafe?
Assignee: nobody → adam
Whiteboard: [webrtc][blocking-webrtc?]
I would prefer it it were a stub, since that way it doesn't cause an exception
Whiteboard: [webrtc][blocking-webrtc?] → [webrtc][blocking-webrtc+]
Priority: -- → P3
Assignee: adam → snandaku
Added one line fix to say RemoveStream is "NOT IMPLEMENTED" in PeerConnection.js.
Attachment #729985 - Flags: review?(adam)
Attachment #729985 - Flags: review?(rjesup)
Whiteboard: [webrtc][blocking-webrtc+] → [webrtc][blocking-webrtc-]
Whiteboard: [webrtc][blocking-webrtc-] → [webrtc][blocking-webrtc+]
Attachment #729985 - Flags: review?(rjesup) → review+
Attachment #729985 - Flags: checkin?(rjesup)
Attachment #729985 - Flags: review?(adam) → review+
Attachment #729985 - Flags: checkin?(rjesup)
https://hg.mozilla.org/mozilla-central/rev/214782bec2a6
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
Whiteboard: [webrtc][blocking-webrtc+] → [webrtc][blocking-webrtc+][qa-]
Flags: in-testsuite-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: