Chrome desktopCapture api can't share another instance of Chrome
Reported by
adi...@cafex.com,
Sep 12
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: 1. Start an instance of Chrome 2. Start another instance of Chrome (using '--user-data-dir=' to create a seperate profile or start Chromium as the second browser instance) 3. Navigate to https://meet.google.com on your first browser instance and join a meeting 4. Click present now to start a screenshare and choose to share a single window. 5. Try and share the second browser instance What is the expected behavior? Chosen window is shared and contents is seen What went wrong? Shared window appears as black. When page is focused it displays correctly however anything that comes up in front of the window (e.g. notification from the notification api) makes the entire window appear as black. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 69.0.3497.81 Channel: stable OS Version: 10.0 Flash Version: Same behaviour happens when using the Chrome extension desktopCapture api. Firefox also has the same behaviour when sharing Chrome, however sharing Firefox or any other browser works fine. Turning off Hardware acceleration on the Chrome window to be shared makes this issue go away. Tested on Windows 7, 10 and macOS 10.13.6, behaviour happens in Windows 7 and 10 but not on Mac
,
Sep 14
,
Sep 21
this looks like issue 778855
,
Sep 27
Thanks for filing the issue! As per comment# 3, this issue seems to be similar to Issue: 778855 . @Reporter: Could you please have a look at this issue(issue: 778855 ) and provide your confirmation if both the issues are similar. Note: CC'ing the owner(miu@chromium.org) with reference to the issue: 778855 to provide further inputs on it. Thanks!
,
Sep 28
It doesn't look like quite the same issue, in 778855 they're attempting to share the same Window as the one being used to start the share. This issue involves attempting to share a different window that's a different instance of Chrome (for example, sharing a window from Chromium, or a Chrome with a different user directory setup)
,
Sep 28
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5
,
Oct 5
"anything that comes up in front of the window (e.g. notification from the notification api) makes the entire window appear as black.", this is working as intended. Due to the limitation on Windows, HW accelerated windows can't be captured by GDI methods. So the only way to share such a window as Chrome, we have to crop it out from a screen capture, which requires the target window on foreground without any occluding. The notification from Chrome itself will be ignored. Not others. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dtapu...@chromium.org
, Sep 12