| commit | a4bcf3d1bd4294fb08d70974a156523720d926d0 | |
| author | jdduke <jdduke@chromium.org> | |
| Fri, 1 May 2015 22:10:30 +0000 (1 15:10 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 1 May 2015 22:11:52 +0000 (1 22:11 +0000) | ||
| tree | c41fd2ecd7c10904df5526ae33dd1b7221da798f | treesnapshot (tar.gz zip) |
| parent | 991ec975f29b57a54d852968d255cb4125f5c4e9 | commitdiff |
Restore simple fling status bookkeeping
Recently, an active fling counter was introduced to track whether a
fling was active in the renderer. This was useful both for filtering
fling cancel events as well as signalling the end of a fling gesture
for telemetry purposes.
However, there appear to be gaps in the fling accounting that don't
appear in telemetry but do appear in the wild, causing issues with
fling-related tap suppression logic. Restore the previous fling
bookkeeping for the GestureEventQueue until the in-flight fling
count is correct for all gesture types.
BUG=483037
Review URL: https://codereview.chromium.org/1113143002
Cr-Commit-Position: refs/heads/master@{#327993}
Recently, an active fling counter was introduced to track whether a
fling was active in the renderer. This was useful both for filtering
fling cancel events as well as signalling the end of a fling gesture
for telemetry purposes.
However, there appear to be gaps in the fling accounting that don't
appear in telemetry but do appear in the wild, causing issues with
fling-related tap suppression logic. Restore the previous fling
bookkeeping for the GestureEventQueue until the in-flight fling
count is correct for all gesture types.
BUG=483037
Review URL: https://codereview.chromium.org/1113143002
Cr-Commit-Position: refs/heads/master@{#327993}