[ChromeOS] Chrome Remote Desktop: mouse position incorrect when not at native resolution
Reported by
johnharr...@gmail.com,
Jul 24 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8172.62.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 Platform: 8172.62.0 (Official Build) stable-channel auron_yuna Steps to reproduce the problem: 1. set display resolution on computer to share to something non-native 2. generate code to share computer with a remote 3. connect with remote. What is the expected behavior? remote will show correct mouse position What went wrong? remote does not show correct mouse position Did this work before? N/A Chrome version: 51.0.2704.106 Channel: stable OS Version: 8172.62.0 Flash Version: Shockwave Flash 22.0 r0 works correctly if resolution is native. Remote was another chromebook with same specifications as the one documented here.
,
Jul 26 2016
,
Jul 26 2016
,
Aug 29 2016
This appears to be a regression: reproduced on 52, but works correctly on 49
,
Sep 23 2016
Per discussion with Erik, I'll take a look at this.
,
Oct 26 2016
,
Apr 16 2018
Any news? Just ran into this as well on Eve when I set my resolution to 1800x1200 on Chrome M65. We're working out issues with a large enterprise customer who needs Chromoting for their customer support. Is there any chance this could be looked at? Thanks!
,
Apr 20 2018
One mediocre workaround: If you remote into a computer exhibiting this problem, use Ctrl + Shift + 0 to reset the shared machine's resolution to native, so you can accomplish what you need.
I suppose it would actually be smarter to use Ctrl + Shift + {+,-} first so you can see what the resolution was before you reset it to native. Then you could return it to the non-native resolution before logging off.
,
Apr 30 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dhadd...@chromium.org
, Jul 26 2016