Re: Bug 26243: where should getUserMedia attach

Thanks all for contributing to this discussion. I conclude that there 
should be only one way: navigator.mediaDevices.getUserMedia.

I'll update the bug accordingly and assign for editing.

Stefan

On 21/08/14 19:25, Peter Thatcher wrote:
> 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 Friday, 22 August 2014 05:58:15 UTC