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

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

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Jun 2016 14:43:38 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-227766459-1466606617-sysbot+gh@w3.org>
Some specs like 
[DOM](https://dom.spec.whatwg.org/#dom-element-webkitmatchesselector) 
and [Geometry](https://drafts.fxtf.org/geometry/#webkitcssmatrix) have
 gone the path of spec'ing both the unprefixed and webkit-prefixed 
APIs. It's pretty likely that everyone could successfully converge on 
that without sacrificing compat. Having only the webkit-prefixed API 
might also be web compatible, but then Edge has to take a risk in 
removing their `navigator.getUserMedia`.

I know of [one 
case](https://html.spec.whatwg.org/#concept-navigator-compatibility-mode)
 where we enshrined diverging behavior on `navigator.vendor` and 
friends because there seemed to be no path forward, but I think that 
should be a last resort.

In the [Intent to implement and ship: Unprefixed 
getUserMedia](https://groups.google.com/a/chromium.org/d/msg/blink-dev/E4LA0P0YYPQ/4LGTKRcDBwAJ)
 I did test Gecko and notice the lack of support for 
`navigator.getUserMedia`, but it's only now that it's clear that you 
really don't want this in Firefox.

If `navigator.getUserMedia` reaches Chrome stable I think it's a done 
deal, it'll never go away. So, you get all the implementors together 
to discuss and decide on this while there are still options on the 
table?

-- 
GitHub Notification of comment by foolip
Please view or discuss this issue at 
https://github.com/w3c/mediacapture-main/issues/368#issuecomment-227766459
 using your GitHub account
Received on Wednesday, 22 June 2016 14:43:40 UTC

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