Issue metadata
Sign in to add a comment
|
Win10 tab capture displays black inner window.
Reported by
d...@tokbox.com,
May 17 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36 Example URL: meet.tokbox.com/win10test Steps to reproduce the problem: 1. https://meet.tokbox.com/win10test, click bottom left monitor icon to share screen 2. Install extension if necessary, share tab 3. Publishing stream with black inner window, visible menu bar/outer frame, visible mouse cursor What is the expected behavior? Entire window and inner window content is rendered in webRTC screen sharing stream. What went wrong? Inner window content is published in webRTC stream as a black frame. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Last checked on Win10 49, worked as expected. Does this work in other browsers? N/A Chrome version: 50.0.2661.94 Channel: stable OS Version: 10.0 Home, Build 10586 Flash Version: Shockwave Flash 21.0 r0
,
May 17 2016
Also has to be maximized.
,
May 17 2016
this is a major issue for my product too.
,
May 17 2016
Hello, this is your friendly blink triage sheriff. I'm assigning this to WebRTC. Just to confirm, this is only reproing in Windows? Is there any chance we can get a reduced test case? Does it require the extension?
,
May 17 2016
It seems to be only on Windows machines regardless of version.
,
May 18 2016
Possible regression of Issue 289779 .
,
May 18 2016
Seeing it on Windows 10 in our WebRTC product. All Chrome windows appear black regardless of maximized state.
,
May 18 2016
Appears to happen in Hangouts, too, if this is the same issue, pictured.
,
May 18 2016
dmun@ - is this also reproducible with the current Canary build?
,
May 18 2016
I've seen this in the Canary build, and also not just on Windows 10, but 7, 8 too.
,
May 18 2016
I personally am actually not seeing this on the latest Beta or Canary on my Win10 machine.
,
May 18 2016
This is a known issue for Chrome 50 but should not happen on a Chrome version 51 or higher. If that's the case get back on this bug with exact version info. [comment deleted and readded since I typed the wrong version info]
,
May 18 2016
Thanks niklase. As per the calendar at https://www.chromium.org/developers/calendar It looks like 51 should be promoted to stable in a couple weeks.
,
May 19 2016
I've Windows 7 running 50.0.2661.102, the issue is different here where it sometimes flicks on/off from a black screen.
,
May 19 2016
mbat@ - if you're still seeing this in the current canary build, can you file a new bug? Per comments #13 and #15, it looks like the originally reported issue is fixed in M51+, so what you're experiencing may have a different root cause. Please reply back with the new bug number, and we'll take a look. Thanks! niklase@ - srnarayanan@ mentioned offline that this could be a dupe of bug 581790 . With that in mind, and based on comments #13 and #15, do you think this bug can be closed?
,
May 19 2016
Yeah I'm pretty sure that this is a dupe, but since comments mention this being seen on canary (where 50 haven't been in a long time) I want to make sure that it doesn't happen on newer versions. Will dupe/close if I don't hear anything more on this bug this week.
,
May 23 2016
Issue 614039 has been merged into this issue.
,
May 23 2016
,
May 26 2016
Issue 613987 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by d...@tokbox.com
, May 17 2016