You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix an issue where touch events were dispatched to the incorrect webview
Was caused by touchscreen_gesture_target_queue_ + prevent default. The
webview target was calculated on TouchStart and pushed to the the queue.
It was removed on its corresponding GestureTapDown. However, if the
TouchStart had default behavior prevented, no GestureTapDown would ever
occur, and the queue would forever have an extra element.
Fixed by converting touchscreen_gesture_target_queue_ to a map with
unique_touch_event_id as keys and gesture target data as values.
Also updates AUTHORS file.
[email protected]
(cherry picked from commit 09a2f88)
Bug: 736623, 739831
Change-Id: If3bf844e2bcfb9a1ca6d6a56cdc7575e0767e6b6
Reviewed-on: https://chromium-review.googlesource.com/547669
Commit-Queue: James MacLean <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Reviewed-by: Ken Buchanan <[email protected]>
Reviewed-by: James MacLean <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#488759}
Reviewed-on: https://chromium-review.googlesource.com/586747
Cr-Commit-Position: refs/branch-heads/3163@{#54}
Cr-Branched-From: ff259ba-refs/heads/master@{#488528}
0 commit comments