Revert "mus: Fix event processing for touch events in unified mode"
This reverts commit 1423331f. Reason for revert: speculative attempt due to unhappy MSan ChromiumOS bot. See also crbug.com/806638. Original change's description: > mus: Fix event processing for touch events in unified mode > > This refines my earlier work done in: http://crrev.com/c/842467 > > Move event target nulling and root location use to WindowTreeClient, to ensure events reach MusUnifiedEventTargeter. > Otherwise, WindowEventDispatcher::GetInitialEventTarget will use the touch gesture recognizer's target (returned by GetPriorityTargetInRootWindow) before performing the mirror display transformation on the event's location. > > Inline DispatchEventToTarget for additional clarity. > > Bug: 805714 > Test: Mus touch events work in Chrome OS's unified desktop mode. > Change-Id: Ic4844c85cc24a9f9885e7705ff27cb57b305d245 > Reviewed-on: https://chromium-review.googlesource.com/887250 > Commit-Queue: Michael Wasserman <msw@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Cr-Commit-Position: refs/heads/master@{#532030} TBR=sky@chromium.org,msw@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 805714 Change-Id: I02333546f91d0d0f495153c8556aa9820612673d Reviewed-on: https://chromium-review.googlesource.com/890841Reviewed-by:Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#532328}
Showing
Please register or sign in to comment