New issue
Advanced search Search tips

Issue 727977 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocked on:
issue 618465



Sign in to add a comment

Update tab_capture_custom_bindings.js to use new MediaDevices API

Project Member Reported by m...@chromium.org, May 31 2017

Issue description

chrome/renderer/resources/extensions/tab_capture_custom_bindings.js uses the legacy (and deprecated) webkitGetUserMedia() API to proxy a chrome.tabCapture extension API call to the renderer. It should use navigator.mediaDevices.getUserMedia() instead (ref: https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia).

Also, it seems that the exception/error bindings adapter code is slightly broken: The |error.message| field from gUM() is always set to the empty string, never anything useful. This causes chrome.runtime.lastError.message to always be just an empty string. This should be fixed such that useful error messages are visible from chrome.runtime.lastError result when the getUserMedia() call fails.
 
Labels: -M-61 M-62
Changing milestone to M62. Please correct of that's wrong.

Comment 2 by m...@chromium.org, Feb 1 2018

Components: Platform>Extensions>API
Labels: TabCapture

Comment 3 by m...@chromium.org, Feb 1 2018

Components: -Blink>GetUserMedia>Tab

Sign in to add a comment