New issue
Advanced search Search tips

Issue 686839 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 696754
issue 548429
issue 706200



Sign in to add a comment

Display configuration animations in mustash

Project Member Reported by kylec...@chromium.org, Jan 30 2017

Issue description

When certain display configuration changes happen, ash first fades the screen to black then does configuration. After configuration is finished the screen fades back in.

This all happens in the browser process in classic ash. In mustash, display configuration will happen in the mus-ws process but the animations will happen in the WM process. We need mus-ws to send an IPC to the WM for the start configuration animation, wait for a response back, try to change the display configuration, then send an IPC to the WM for the end configuration animation.
 
Labels: mustash-1
Do we really need this for Q1?

It looked like multi-display support is for Q2.

Labels: -mustash-1
It's very closely related to Display Settings page. If that isn't a Q1 priority then no.

Comment 4 by sky@chromium.org, Mar 27 2017

Labels: mustash-2

Comment 5 by sky@chromium.org, Mar 27 2017

This includes code such as RootWindowTransformer.

Comment 6 by sky@chromium.org, Mar 27 2017

And most likely all the code in ash/rotator.

Comment 7 by sky@chromium.org, Mar 28 2017

Blocking: 706200

Comment 8 by sky@chromium.org, Mar 29 2017

Blocking: 696754
Components: Internals>Services>Ash
Labels: -Proj-Mustash-Mash-WM
Labels: -Proj-Mustash-Mus-WS
Deprecating Proj-Mustash-Mus-WS label in favor of Components.

Sign in to add a comment