This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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.
Sent a mail to the list on July 7th to get more input.
The conclusion of the list discussion is that there should be only one way: #2: NavigatorUserMedia.MediaDevices.getUserMedia(); Assigning for editing.
Proposed fix: https://github.com/w3c/mediacapture-main/commit/30c1812084ceee87761f2ee4af9a123b0a604ec6