Evaluate if MouseCursorEventFilter needs to be made to work for mash |
||||||
Issue descriptionIt's used for unified and extend desktop modes, and may need to move to mus.
,
May 4 2017
,
May 5 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a5888e81e68aff997094e675cccfe09c559d5f4b commit a5888e81e68aff997094e675cccfe09c559d5f4b Author: sky <sky@chromium.org> Date: Fri May 05 17:56:31 2017 chromeos: enable MouseCursorEventFilter for mushrome Now that mushrome creates a WindowTreeTreeHostManager it can create a MouseCursorEventFilter. Also updates test expectation as a bunch of tests were relying on this. BUG= 714150 , 706474 TEST=covered by tests R=jamescook@chromium.org Review-Url: https://codereview.chromium.org/2868463002 Cr-Commit-Position: refs/heads/master@{#469715} [modify] https://crrev.com/a5888e81e68aff997094e675cccfe09c559d5f4b/ash/shell.cc [modify] https://crrev.com/a5888e81e68aff997094e675cccfe09c559d5f4b/testing/buildbot/filters/ash_mus_unittests.filter
,
May 5 2017
MouseCursorEventFilter is now enabled in mushrome, so I'm updating the title to reflect we need to figure this out for mash now. I suspect we'll need MouseCursorEventFilter for mash as well, but that will require some restructuring, and is blocked on getting mash to support simplified display management.
,
May 5 2017
,
Jun 21 2017
Simplified display management means this is now enabled.
,
Jan 22 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kylec...@chromium.org
, Mar 29 2017