screenshare issue when sharing in a multi-monitor environment
Reported by
dav...@anymeeting.com,
Dec 22 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. have 2 monitors with different resolution 2. have a webrtc webapp on the higher resolution monitor and try to share the higher resolution screen and the lower resolution screen and check chrome://webrtc-internal to see what the sent resolution is. you should see 2 different resolutions for the 2 cases. 3. have the webrtc webapp browser be in the lower resolution monitor, do the same as the above step, screenshare the higher/lower resolution screen and check chrome://webrtc-internals for the sent resolution. you'll see now that the sent resolution for both is constrained to the lower resolution. 3. What is the expected behavior? screenshare resolution of monitor screen should not be constrained to the lower resolution if the browser hosting the webrtc webapp is in the lower resolution monitor What went wrong? it constrained the resolution when no constraint is given in the getusermedia request Did this work before? N/A Does this work in other browsers? N/A Chrome version: 63.0.3239.84 Channel: stable OS Version: 10.0 Flash Version:
,
Jan 1 2018
Unable to reproduce the issue on reported chrome version 63.0.3239.84 and on the latest canary 65.0.3309.0 using Windows 10 with the below mentioned steps.
1. Launched chrome
(From main system/monitor which is of high resolution)
2. Navigated to https://appr.tc/ (For establishing a web rtc connection)
3. Gave the input values on the remote system and established the connection.
4. Navigated to chrome://webrtc-internals on Main and remote desktop.
We are Unable to find any information upon navigating to chrome://webrtc-internals about resolution of the shared screen.
@Reporter: Could you please let us know whether we have missed any steps in reproducing the issue. Please share the URL through which the connection is being established from your end. Any further inputs helps us to triage the issue in a better way.
Thanks!
,
Jan 9 2018
,
Jan 9 2018
davidl@: Additional question. What were the resolutions of the two monitors in your experiment?
,
Nov 9
Closing this issue due to lack of user feedback and assuming that issue got fixed from their end. Please feel fee to raise a new issue if the issue is still reproducible on latest chrome builds. Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Dec 26 2017