Certain display layouts prevent the mouse moving between screens
Reported by
dawid.ku...@displaylink.com,
May 25 2016
|
||||||||||
Issue descriptionChrome Version: 52.0.2727.0 (Official Build) dev (64-bit) Chrome OS Version: 8302.0.0 (Official Build) dev-channel link Chrome OS Platform: Helium <b>Network info: <network, encryption type, router model (if known)></b> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Attach two external monitors (one normally and second with e.g. DL2 device) (2) Set layout as presented in attached screenshot; and some form of pyramid; note that all screens are connecting (3) Move cursor across all three monitors Expected Result: Be able to move cursor between all three monitors in all directions, this is: - Internal Monitor <-> PHL 274E5 - Internal Monitor <-> Acer K24HQK - PHL 27E5 <-> Acer K24HQK Actual Result: In currect situation it is possible to move cursor only between: - Internal Monitor <-> PHL 274E5 - Internal Monitor <-> Acer K24HQK but NOT between: - PHL 27E5 <-> Acer K24HQK Please note the orange line in the 'Manage display' window at the bottom of Internal Display square - this appears to be the allowed crossing line. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? The only thing that user can do is to move cursor through the 'Internal display'. Please provide any additional information below. Attach a screen shot or log if possible. To produce this layout: -first move PHL display under the Internal, that it will overlap with it around 50% -then move Acer display so it will connect with both Internal and PHL.
,
Jun 16 2016
oshima@ this seems like something you would be able to fix?
,
Jun 20 2016
,
Jun 30 2016
,
Jun 30 2016
,
Oct 20 2016
This is still happening with R55. Is there a chance this will be fixed soon?
,
Nov 15 2016
afakhry@, can you tale a quick look at this? Please ping me re where to look.
,
Dec 1 2016
,
Dec 1 2016
I was able to repro. The two bottom displays in the screen shot in #0 are intersecting rather than touching. This causes display::ComputeBoundary() which is used to create the warp region between those two displays to fail. @stevenjb, is that a bug in the display layout options page?
,
Feb 1 2017
CL: https://codereview.chromium.org/2573673003 has landed at https://chromium.googlesource.com/chromium/src/+/6c80a875d8534f5f9d965a9808446655b5f4e0a2
,
Feb 15 2017
verified in 9000.85.0/56.0.2924.99. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by bhthompson@chromium.org
, Jun 16 2016