New issue
Advanced search Search tips

Issue 794612 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 731255



Sign in to add a comment

mus: Swapping primary display causes strange input/display problems

Project Member Reported by msw@chromium.org, Dec 13 2017

Issue description

mus: Swapping primary display causes strange input/display problems

On ToT@#523631 run chrome --mus with two displays (on device or desktop)
(1) Run "chrome --mus --screen-config=500x500,500x500 --use-gl=egl"
(2) Navigate to about:settings/display and select the second/external display.
(3) Next to "Screen" select "Primary display" from the dropdown.
(4) Try to interact with the UI on each of the displays.
Expected: Interaction works as normal.
Actual: A variety of strange issues, I'll try to elaborate below.

On linux desktop chromeos: input seems to targeted at the opposite display.
(clicking x,y on display1 seems to target x,y on display2, and vice versa) 

On device (cyan): sometimes the display(s) goes black except for the cursor.
Sometimes the display might show its last (stale) frame indefinitely.
When the displays show content, the input is sometimes misdirected.
(the device may need restart, or even a new profile/wipe to use that display again)
 
Owner: kylec...@chromium.org
Status: Assigned (was: Untriaged)
kylechar@ please triage

Comment 2 by sky@chromium.org, Dec 13 2017

Blocking: 731255
Owner: msw@chromium.org
The mouse event locations appear fine but ash is drawing to the wrong gfx::AcceleratedWidget after you swap the primary display. It works better when the buffers are the same size and is more broken when the buffers are different sizes.
Project Member

Comment 4 by bugdroid1@chromium.org, Jan 10 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/30c6fd4425ca6f2b2c31c5d949805ae7cc40afc1

commit 30c6fd4425ca6f2b2c31c5d949805ae7cc40afc1
Author: Mike Wasserman <msw@chromium.org>
Date: Wed Jan 10 21:26:28 2018

mus: Swap WindowTreeHostMus AcceleratedWidgets on display root swap.

This uses the correct platform display for the swapped display roots.

Bug:  794612 
Test: Make the 2nd display primary in about:settings/display with --mus
Change-Id: I9eac5ea0123061dd0147d7e329fec816e55d744e
Reviewed-on: https://chromium-review.googlesource.com/857601
Commit-Queue: Michael Wasserman <msw@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#528429}
[modify] https://crrev.com/30c6fd4425ca6f2b2c31c5d949805ae7cc40afc1/ui/aura/mus/window_tree_client.cc
[modify] https://crrev.com/30c6fd4425ca6f2b2c31c5d949805ae7cc40afc1/ui/aura/mus/window_tree_client_unittest.cc

Comment 5 by msw@chromium.org, Jan 10 2018

Status: Fixed (was: Assigned)
Should be fixed, hopefully I'll also be able to test on device soon.
Components: -Internals>MUS Internals>Services>WindowService

Sign in to add a comment