| commit | 9322a2437f8141a8b4e9556aca454a66f97338c1 | |
| author | yfriedman <yfriedman@chromium.org> | |
| Wed, 29 Oct 2014 00:28:49 +0000 (28 17:28 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 29 Oct 2014 00:29:06 +0000 (29 00:29 +0000) | ||
| tree | 2a18cfd07af9831a6067e75c321dac3dec8a11f5 | treesnapshot (tar.gz zip) |
| parent | b022fc3af337186a85556e75fe78fb0afded68f5 | commitdiff |
Remove TestTouchUtils.clickById.
It's inherently a bad API as it relies on TouchUtils.clickView which
simulates clicks on the screen. That approach can lead to INJECT_EVENTS
issues if the screen turns off or a view pops in front of chrome. The
alternative is to use event propagation to a specific view such as in
TouchCommon.singleClickView
BUG=427031
Review URL: https://codereview.chromium.org/678423004
Cr-Commit-Position: refs/heads/master@{#301744}
It's inherently a bad API as it relies on TouchUtils.clickView which
simulates clicks on the screen. That approach can lead to INJECT_EVENTS
issues if the screen turns off or a view pops in front of chrome. The
alternative is to use event propagation to a specific view such as in
TouchCommon.singleClickView
BUG=427031
Review URL: https://codereview.chromium.org/678423004
Cr-Commit-Position: refs/heads/master@{#301744}
| content/public/test/android/javatests/src/org/chromium/content/browser/test/util/TestTouchUtils.java | diffblobblamehistory |