W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2014

Re: Bug 26243: where should getUserMedia attach

From: Peter Thatcher <pthatcher@google.com>
Date: Thu, 21 Aug 2014 10:24:24 -0700
Message-ID: <CAJrXDUEEDvA4rDZtLWW3Nb3ab=mEhVKf=9_OCzrfui5xdtXtbw@mail.gmail.com>
To: Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
I agree with other comments that we should just have one, and it
should be navigator.mediaDevices.getUserMedia.   The existing
implementations can leave navigator.getUserMedia during a transition
period.  We're already doing similar transition periods for things
like constraints and other API changes.

On Mon, Jul 7, 2014 at 5:31 AM, Stefan HÃ¥kansson LK
<stefan.lk.hakansson@ericsson.com> wrote:
> Since day one of WebRTC (this was before we spun off the local media
> things into a TF) the way to get access to camera and microphone has been:
>
> navigator.getUserMedia(....);
>
> from the spec version of June 19th [1] it is also possible to do
>
> navigator.mediaDevices.getUserMedia(....);
>
> Shijun filed a bug on that we should keep one way (not both) [2].
>
> The comments so far seem to indicate that while
> navigator.mediaDevices.getUserMedia is more logical we should only keep
> the old navigator.getUserMedia method since many apps are using it. But
> there has also been the comment that this is behind vendor prefix so
> changing does not have that big consequences (and perhaps
> implementations could support the old prefixed way for a long time even
> if the spec changes).
>
> I'd like some more discussion, and a conclusion. What should the spec say?
>
> Stefan
>
> [1] http://dev.w3.org/2011/webrtc/editor/archives/20140619/getusermedia.html
> [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26243
>
>
>
Received on Thursday, 21 August 2014 17:25:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:29 UTC