Issue metadata
Sign in to add a comment
|
Desktop capturer screen preview name not match screen order in OS
Reported by
serejkas...@gmail.com,
Mar 20 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Steps to reproduce the problem: 1. Collect screens to share using desktopCapturer API 2. Observe screen names. What is the expected behavior? "Screen 1" should match main screen in OS. What went wrong? Screen id in name given randomly. Did this work before? N/A Chrome version: 65.0.3325.162 Channel: stable OS Version: OS X 10.12.6 Flash Version: Sample app that could help to reproduce issue https://chrome.google.com/webstore/detail/desktop-capture-sample/mhkidniocjdaiddjckopkigjmjbadfji
,
Mar 20 2018
It is reproducible also with Windows 7 or 10 and chrome 65
,
Mar 20 2018
,
Mar 21 2018
,
Apr 12 2018
Able to reproduce the issue on reported version 65.0.3325.162, the issue is seen on latest stable# 65.0.3325.181, beta# 66.0.3359.81 and latest chrome# 67.0.3394.0 using Windows-10, hence providing manual Bisect Info from Omaha proxy Note: While running bisect on the tool, the builds which got invoked got crashed immediately, hence providing manual bisect info, as ET team has dual monitor setup only on Windows-10 hence not updating the behaviour related to Ubuntu 14.04 and Mac 10.12.6. Bisect Info: ================ Good build: 61.0.3150.0 Bad build: 61.0.3152.0 Change Log: https://chromium.googlesource.com/chromium/src/+log/61.0.3150.0..61.0.3152.0?pretty=fuller&n=10000 Commit: https://chromium.googlesource.com/chromium/src/+/56efe642b5d1fc400ac7f34451d9a540f9d30fbb Review-Url: https://codereview.chromium.org/2961193002 @zijiehe: Please confirm the issue and help in re-assigning if it is not related to your change. Thanks!
,
Apr 12 2018
I believe the change mentioned in #c5 does not relate to this issue. But the order of the screens is controlled by screen capturer component in WebRTC. Brave Yao (BraveYao@) may have a look at this issue. But I doubt the importance of it. The screen names from display configuration do not match the orders from Windows API. I believe the order returned by Windows API usually depends on the video adapters.
,
Apr 23 2018
Can't reproduce this issue on either Win10 laptop + dock(thunderbolt) or Win10 desktop. In my setting-up, the screen sequence is decided by the connection jacks, so does the desktopCapture enumeration. See the enclosed screenshot. I wonder if any USB display adapter is used in your environment?
,
Apr 23 2018
,
Apr 23 2018
> I wonder if any USB display adapter is used in your environment? DVI, VGA, HDMI, DP. Did you tried to change order? does WebRTC sample reflect correctly this changes? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dimitrio...@gmail.com
, Mar 20 2018688 KB
688 KB View Download