New issue
Advanced search Search tips

Issue 649312 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 297173
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Is black capture of other Chromium-based application screen

Reported by bellface...@gmail.com, Sep 22 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2868.0 Safari/537.36

Steps to reproduce the problem:
ChromeとElectronとNW.js、それぞれにおいてchooseDesktopMedia()(ElectronではdesktopCapturer.getSources())を実行する。

What is the expected behavior?
自分以外のChromiumベースのアプリケーションのキャプチャ映像が真っ黒になる。(選択画面で選択した後getUserMedia()でストリームを取得しても真っ黒のまま)

What went wrong?
真っ黒な映像ではなく、画面に表示されているそのままの映像を取得したい。

Did this work before? N/A 

Chrome version: 55.0.2868.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

添付画像は、

OS: Windows 10 64bit (14393.105)
Chrome: 55.0.2868.0 canary (64-bit)
Electron: 1.4.0
NW.js: 1.8.0-beta 1 (Chrome: 54, Node: 6.5.0)

で実行した時のスクリーンショット。
 
chooseDesktopCapture_bug.png
115 KB View Download
Components: -Blink Blink>GetUserMedia
Labels: Needs-Feedback
[triage] bellface.inc.develop@ what application are you trying to capture?
Cc: sergeyu@chromium.org
Summary: Is black capture of other Chromium-based application screen (was: 他のChromiumベースのアプリケーションの画面のキャプチャーが真っ黒になる)
sergeyu: Is it possible that windows from other Chromium-based applications are not possible to capture with the Screen capture API?

For convenience, the translated bug description: https://translate.google.com/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D649312&edit-text=&act=url

Mergedinto: 297173
Status: Duplicate (was: Unconfirmed)
This is known limitation in the screen capturer combined with Aura. See  bug 289779 . That bug is closed because we were able to work around for windows created by the same browser instance. The root cause is tracked by  bug 297173 .

Sign in to add a comment