Display configuration animations in mustash |
|||||||
Issue descriptionWhen 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.
,
Jan 31 2017
Do we really need this for Q1? It looked like multi-display support is for Q2.
,
Jan 31 2017
It's very closely related to Display Settings page. If that isn't a Q1 priority then no.
,
Mar 27 2017
,
Mar 27 2017
This includes code such as RootWindowTransformer.
,
Mar 27 2017
And most likely all the code in ash/rotator.
,
Mar 28 2017
,
Mar 29 2017
,
Apr 19 2018
,
Apr 24 2018
Deprecating Proj-Mustash-Mus-WS label in favor of Components. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kylec...@chromium.org
, Jan 30 2017