- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2016 22:35:16 +0000
- To: public-media-capture-logs@w3.org
@RByers @foolip Note: `navigator.getUserMedia` is *incompatible* with
`navigator.webkitGetUserMedia` because the latter supports a
Chrome-only constraints syntax (@alvestrand correct me if I'm wrong) .
So Edge couldn't have used it.
Legacy compat is quite messy, and Chrome's new
`navigator.getUserMedia` does more harm than good:
The only compat I see it fixing is a site *not* using the newer
`navigator.mediaDevices.getUserMedia`, yet at the same time using
modern spec constraints, and never testing their page in Chrome. Given
marketshare, I find that hard to believe. (Firefox docs and warnings
are heavily pushing `navigator.mediaDevices.getUserMedia`).
On the flipside, I'm surprised Google isn't more worried about this
going to release, given that it looks to break a lot of users who
depend on their old constraints format. Specifically, if they did
this:
```js
navigator.getUserMedia = navigator.getUserMedia ||
navigator.webkitGetUserMedia ||
navigator.mozGetUserMedia;
```
Then their constraints are now broken. But if they did this:
```js
navigator.getUserMedia = navigator.webkitGetUserMedia ||
navigator.getUserMedia ||
navigator.mozGetUserMedia;
```
then it is not.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at
https://github.com/w3c/mediacapture-main/issues/368#issuecomment-227898180
using your GitHub account
Received on Wednesday, 22 June 2016 22:35:21 UTC