diff options
| author | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-02-21 17:41:40 +0000 |
|---|---|---|
| committer | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-02-21 17:41:40 +0000 |
| commit | 85e92459c27137a7b5aa764e6e4a682aef62bb2f (patch) | |
| tree | 684d294f3d050b2726bba25ea9389db59a9a6455 /build | |
| parent | 66a4213717da7989915ba0950f594bb49c8c7a25 (diff) | |
| download | chromium_src-85e92459c27137a7b5aa764e6e4a682aef62bb2f.zip chromium_src-85e92459c27137a7b5aa764e6e4a682aef62bb2f.tar.gz chromium_src-85e92459c27137a7b5aa764e6e4a682aef62bb2f.tar.bz2 | |
touch: Change the behaviour of compositor-thread hittesting for touch events.
The ACK state of each touch-point is maintained individually. So, if a touch
point has no consumer for the touch-start event, then no subsequent move or
end events for that point will be dispatched to the renderer. However, during
this touch sequence, if any new touch-point is pressed, then the press event
will be dispatched to the renderer. Whether subsequent move/end events for
the second touch-point are dispatched to the renderer depends entirely on the
ACK state for the press-event of the second touch-point, and is completely
independent of the ACK state of the first touch point.
BUG=174762
Review URL: https://codereview.chromium.org/12320004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183831 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions