| commit | 92801d31b071372560733001086a6e31f58e1ae0 | |
| author | jdduke <jdduke@chromium.org> | |
| Wed, 8 Apr 2015 21:40:02 +0000 (8 14:40 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 8 Apr 2015 21:40:35 +0000 (8 21:40 +0000) | ||
| tree | 2567b1cb594f05389f95214f8182fd7fc68cf4ed | treesnapshot (tar.gz zip) |
| parent | 057915a0e5410b4bb3b25a53deedcfd69b33a77b | commitdiff |
[Android] Properly filter GestureFlingCancel events
The browser will drop GestureFlingCancel events when it believes the
renderer has no active fling animations. However, this filtering would
report the event as "consumed", inadverently triggering tap suppression
logic for the subsequent tap.
Instead, report "no consumer exists" for the filtered GestureFlingCancel
events, avoiding spurious tap suppression.
BUG=474882
Review URL: https://codereview.chromium.org/1074553002
Cr-Commit-Position: refs/heads/master@{#324288}
The browser will drop GestureFlingCancel events when it believes the
renderer has no active fling animations. However, this filtering would
report the event as "consumed", inadverently triggering tap suppression
logic for the subsequent tap.
Instead, report "no consumer exists" for the filtered GestureFlingCancel
events, avoiding spurious tap suppression.
BUG=474882
Review URL: https://codereview.chromium.org/1074553002
Cr-Commit-Position: refs/heads/master@{#324288}