To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
The API owners met to discuss this yesterday. How does this relate to the previous intent? I take it this intent covers only adding the navigator.mediaDevices.getUserMedia() method, and not involving Blink-in-JS?Since the existing method is navigator.webkitGetUserMedia() and isn't promise-based, it sounds like we'll have to wait until virtually all WebRTC code in the wild has been converted to the new API, making it pretty hard to remove the prefixed API.
I don't have a solution for this, but we should add a use counter for navigator.webkitGetUserMedia() and then deprecate it unless usage is already hopelessly high.
The nice thing about this particular API is that it is an *additional* API, not a change to an API. There's no technical issue with supporting both at the same time (apart from API clutter).Formalistically, the previous intent was for the WebRTC PeerConnection object's overloaded functions (which expose a couple of interesting issues); this one is strictly for the Navigator.mediaDevices.getUserMedia function (which does not change the navigator.getUserMedia function at all).On Wed, Jun 24, 2015 at 10:12 AM, Philip Jägenstedt <phi...@opera.com> wrote:The API owners met to discuss this yesterday. How does this relate to the previous intent? I take it this intent covers only adding the navigator.mediaDevices.getUserMedia() method, and not involving Blink-in-JS?Since the existing method is navigator.webkitGetUserMedia() and isn't promise-based, it sounds like we'll have to wait until virtually all WebRTC code in the wild has been converted to the new API, making it pretty hard to remove the prefixed API.I don't understand this comment.... we'll have to use-count the prefixed API, naturally. For full conformance, we should also support the non-prefixed old API, since this is specified in the standard (and use-count that).A huge number of the code in the wild is using the "getUserMedia = navigator.getUserMedia || navigator.webkitGetUserMedia || navigator.mozGetUserMedia" pattern, so if we implement the old API unprefixed, the use count for webkitGetUserMedia should drop pretty fast.(The ones that use our webrtc/adapter solution will actually use the promise-based function for clients that call our helper function that shims promises if they aren't in the platform.)But only measurement will show what happens.
I don't have a solution for this, but we should add a use counter for navigator.webkitGetUserMedia() and then deprecate it unless usage is already hopelessly high.There is already an use-counter on navigator.webkitGetUserMedia(). I'll note that we need an use counter for navigator.mediaDevices.getUserMedia too.(Note: The reason for the timing of the intent-to-implement is that as part of figuring out whether to use blink-in-JS, v8-extra or just C++ code, I implemented this particular function in C++, and it worked. It would be nice to get this code submitted before I go on vacation, so that it's in the codebase.)