MoveEventHandler should be --mash specific |
|||
Issue descriptionWire up non-client cursors in window-service as a library I'm stubbing out this behavior from the original window service for now in: https://chromium-review.googlesource.com/c/chromium/src/+/1055658/6/ash/wm/move_event_handler.cc We'll need something to replace the WindowManagerClient::SetNonClientCursor.
,
Jun 5 2018
In looking at this a bit more, we shouldn't need MoveEventHandler at all for ws2. I'll make this bug become that.
,
Jun 6 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3af7b2a2028fc9d5f128a06e2b0174c107f29242 commit 3af7b2a2028fc9d5f128a06e2b0174c107f29242 Author: Scott Violet <sky@chromium.org> Date: Wed Jun 06 14:52:13 2018 chromeos: makes MoveEventHandler --mash specific It's not applicable to ws2 (because the pre-target handlers installed by ash take care of it). BUG= 842295 TEST=none Change-Id: I57ae1c684580233233bff13186560c2790f56c79 Reviewed-on: https://chromium-review.googlesource.com/1088128 Reviewed-by: Michael Wasserman <msw@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#564888} [modify] https://crrev.com/3af7b2a2028fc9d5f128a06e2b0174c107f29242/ash/wm/move_event_handler.cc [modify] https://crrev.com/3af7b2a2028fc9d5f128a06e2b0174c107f29242/ash/wm/non_client_frame_controller.cc
,
Jun 6 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by msw@chromium.org
, May 14 2018