Closed
Bug 794668
Opened 12 years ago
Closed 12 years ago
Add createFakeMediaStream to gUM
Categories
(Core :: WebRTC, defect)
Tracking
()
VERIFIED
FIXED
mozilla18
People
(Reporter: anant, Assigned: anant)
References
Details
(Whiteboard: [getUserMedia])
Attachments
(1 file)
(deleted),
patch
|
jesup
:
review+
|
Details | Diff | Splinter Review |
We have createFakeMediaStream as part of PeerConnection, but as part of cleaning up those patches, we're going to remove it from there and add similar functionality to getUserMedia instead. We'll start by exposing it to chrome only (just like the device: option, maybe fake:true).
Comment 1•12 years ago
|
||
(In reply to Anant Narayanan [:anant] from comment #0)
> We have createFakeMediaStream as part of PeerConnection, but as part of
> cleaning up those patches, we're going to remove it from there and add
> similar functionality to getUserMedia instead. We'll start by exposing it to
> chrome only (just like the device: option, maybe fake:true).
Could we make use of this for automated tests with gUM & PeerConnection?
Assignee | ||
Comment 2•12 years ago
|
||
{fake:true} support for getUserMedia, also exposed to content, as I don't think there's any harm, in fact it might be quite useful :-)
Attachment #666084 -
Flags: review?(rjesup)
Updated•12 years ago
|
Attachment #666084 -
Flags: review?(rjesup) → review+
Updated•12 years ago
|
Whiteboard: [getUserMedia]
Assignee | ||
Comment 3•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/67f974b861f5
https://hg.mozilla.org/integration/mozilla-inbound/rev/ab46c9bd4e0b
The first patch had a typo as a result of fixing a merge conflict, fixed in the second commit.
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/67f974b861f5
https://hg.mozilla.org/mozilla-central/rev/ab46c9bd4e0b
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
Comment 5•12 years ago
|
||
Verified on 10/4 build. And now I know how to get the automation up and running here. Sweet.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•