This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26243 - Do we need getUserMedia() on MediaDevices?
Summary: Do we need getUserMedia() on MediaDevices?
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-30 21:15 UTC by Shijun Sun
Modified: 2014-08-22 08:54 UTC (History)
3 users (show)

See Also:

Attachments

Description Shijun Sun 2014-06-30 21:15:41 UTC 
Open a bug to track the topic on the mailing list.

In the latest version of the draft, there are two ways to call getUserMedia() within the NavigatorUserMedia.

#1: NavigatorUserMedia.getUserMedia();
#2: NavigatorUserMedia.MediaDevices.getUserMedia();

Based on previous discussions on the mailing list, a good reason to keep NavigatorUserMedia.getUserMedia() is that there are implementations and sites using it already.  Although MediaDevices.getUserMedia() looks nicer, but there seems no clear value keeping two options.
Comment 1 Adam Bergkvist 2014-07-01 08:18:47 UTC 
Yes, we should probably only have one option in the spec, but I guess implementations will leave the vendor prefixed getUserMedia() on NavigatorUserMedia regardless if we move the function to MediaDevices or not.
Comment 2 Stefan Hakansson LK 2014-07-07 13:04:30 UTC 
Sent a mail to the list on July 7th to get more input.
Comment 3 Stefan Hakansson LK 2014-08-22 06:02:43 UTC 
The conclusion of the list discussion is that there should be only one way: 

#2: NavigatorUserMedia.MediaDevices.getUserMedia();

Assigning for editing.