W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > June 2016

[mediacapture-main] Remove navigator.getUserMedia from the spec.

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 Jun 2016 18:38:15 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issues.opened-161509630-1466534294-sysbot+gh@w3.org>
jan-ivar has just created a new issue for 
https://github.com/w3c/mediacapture-main:

== Remove navigator.getUserMedia from the spec. ==
We said we'd give it two years. I think it is time.

Chrome is [on the cusp 
of](https://bugs.chromium.org/p/chromium/issues/detail?id=607439#c8) 
unprexing `navigator.webkitGetUserMedia`, effectively introducing a 
new `navigator.getUserMedia` API. but why add a ***new*** legacy API?

We want people to converge around 
`navigator.mediaDevices.getUserMedia`, not this.

Firefox took a different approach [ten months 
ago](https://bugzilla.mozilla.org/show_bug.cgi?id=1155923), 
unprefixing everything *but* *navigator.mozGetUserMedia* which we show
 a deprecation warning on, directing people to use 
*navigator.mediaDevices.getUserMedia*. Firefox recognized that legacy 
is for actual legacy code.

There is no interop reason, since all legacy code does something like 
this:

     navigator.getUserMedia = navigator.getUserMedia ||
                              navigator.webkitGetUserMedia ||
                              navigator.mozGetUserMedia;

We're now [feeling 
pressure](https://bugzilla.mozilla.org/show_bug.cgi?id=1279936) to 
implement `navigator.getUserMedia` which would send the wrong signal.

Lets remove this for good.

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-main/issues/368 using your GitHub 
account
Received on Tuesday, 21 June 2016 18:38:17 UTC

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