| commit | 913e8928cc9942539aef9aa5bb4ce40148102fca | |
| author | mustaq <mustaq@chromium.org> | |
| Wed, 9 Sep 2015 20:15:36 +0000 (9 13:15 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 9 Sep 2015 20:16:20 +0000 (9 20:16 +0000) | ||
| tree | f0e9686f9b603a2e9dafa7ccdcdb2cb5185f6204 | treesnapshot (tar.gz zip) |
| parent | fb3a1b1a1b4b9fce45db11891c05edc1b853375e | commitdiff |
Improved eventSender handling of non-consecutive touch ids.
After event_sender sees a sequence of touch-cancels or
touch-releases that makes the current touch ids
non-consecutive, it can create duplicate touch-ids for newly
added touch points. See the bug for details. This CL fixes
this problem.
Moreover, event_sender cleans its cache of released touches
but not the canceled ones in SendCurrentTouchEvent. This CL
takes care of this too.
BUG=529807
Review URL: https://codereview.chromium.org/1317733006
Cr-Commit-Position: refs/heads/master@{#347990}
After event_sender sees a sequence of touch-cancels or
touch-releases that makes the current touch ids
non-consecutive, it can create duplicate touch-ids for newly
added touch points. See the bug for details. This CL fixes
this problem.
Moreover, event_sender cleans its cache of released touches
but not the canceled ones in SendCurrentTouchEvent. This CL
takes care of this too.
BUG=529807
Review URL: https://codereview.chromium.org/1317733006
Cr-Commit-Position: refs/heads/master@{#347990}
| components/test_runner/event_sender.cc | diffblobblamehistory |