New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 614660 link

Starred by 5 users

Issue metadata

Status: Verified
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Certain display layouts prevent the mouse moving between screens

Reported by dawid.ku...@displaylink.com, May 25 2016

Issue description

Chrome 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.

 
Screenshot 2016-05-25 at 11.01.04 - Display 1.png
305 KB View Download
Cc: marc...@chromium.org
Owner: osh...@chromium.org
Status: Assigned (was: Unconfirmed)
oshima@ this seems like something you would be able to fix?

Comment 3 by dchan@google.com, Jun 20 2016

Components: OS>Kernel>Graphics UI>Shell>ExtendedDesktop
Components: OS>Kernel>Display
Components: -OS>Kernel>Graphics
This is still happening with R55. Is there a chance this will be fixed soon?

Comment 7 by osh...@chromium.org, Nov 15 2016

Labels: -Pri-3 M-56 Pri-2
Owner: afakhry@chromium.org
afakhry@, can you tale a quick look at this? Please ping me re where to look.
Status: Started (was: Assigned)
Cc: steve...@chromium.org osh...@chromium.org
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?
Status: Verified (was: Fixed)
verified in 9000.85.0/56.0.2924.99. 

Sign in to add a comment