Attempt to fix mouse input issues after a sequence of touch presses.

Attempt to fix mouse input issues after a sequence of touch presses.

Users have reported mouse cursor vanishing and thus being unable to click anywhere in Chrome after
performing a sequence of touch operations. The mouse cursor being hidden is normal and is done by Windows.
However mouse events are not processed because we have pending touch events in our list.

The touch event generation code has a bug where in it assumes the touch downs/ touch releases and moves would
come in separately. However as per msdn releases and moves can be combined into one event which may explain
the pending touch events. When we receive a release we erase the touch events associated with one ID from our list.
If the touch release is combined with the move then this code would not execute thus causing the problem.

BUG=513969
R=sky

Committed: https://crrev.com/87d21af26764b63953c6bce39fb1119b4ee661ff
Cr-Commit-Position: refs/heads/master@{#345706}

[ananta, 2015-08-26 01:50:39]

ananta@chromium.org changed reviewers:
+ sky@chromium.org

[sky, 2015-08-26 15:36:50]

LGTM

[ananta, 2015-08-26 21:52:27]

The CQ bit was checked by ananta@chromium.org

[ananta, 2015-08-26 21:52:27]

The patchset sent to the CQ was uploaded after l-g-t-m from sky@chromium.org
Link to the patchset: https://codereview.chromium.org/1318653002/#ps20001
(title: "Pass the correct input id to release touch state during touch release")

[commit-bot: I haz the power, 2015-08-26 21:53:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1318653002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1318653002/20001

[commit-bot: I haz the power, 2015-08-26 22:40:31]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-08-26 22:41:51]

Patchset 2 (id:??) landed as
https://crrev.com/87d21af26764b63953c6bce39fb1119b4ee661ff
Cr-Commit-Position: refs/heads/master@{#345706}