Defer flushing the touch queue when all touch handlers removed

Defer flushing the touch queue when all touch handlers removed

Currently, the touch event queue will flush itself when it's notified
that all touch handlers have been removed. However, this effectively
overrides the ack of any outstanding touch that is being handled. In
particular, the touch may have been the cause of handler removal *and*
been preventDefault'ed, in which case we should respect the
preventDeafult.

Defer flushing the queue when all handlers have been removed, instead
waiting for any outstanding touch ack. Any additional pending events
will be automatically flushed when the ack is received.

BUG=406916
Committed: https://crrev.com/2d5f6468dd9b3ac1738f35e6de1acfc681412bf2
Cr-Commit-Position: refs/heads/master@{#292685}

[jdduke (slow), 2014-08-28 23:09:04]

jdduke@chromium.org changed reviewers:
+ rbyers@chromium.org

[jdduke (slow), 2014-08-28 23:09:04]

rbyers@: PTAL, thanks.

[Rick Byers, 2014-08-29 15:17:26]

thanks! lgtm

[jdduke (slow), 2014-08-29 15:19:57]

The CQ bit was checked by jdduke@chromium.org

[commit-bot: I haz the power, 2014-08-29 15:20:49]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jdduke@chromium.org/521453002/40001

[jdduke (slow), 2014-08-29 15:21:12]

The CQ bit was unchecked by jdduke@chromium.org

[jdduke (slow), 2014-08-29 15:21:26]

On 2014/08/29 15:21:12, jdduke wrote:
> The CQ bit was unchecked by mailto:jdduke@chromium.org

Looks like I need to update a RWHVAura unit test.

[jdduke (slow), 2014-08-29 15:28:50]

jdduke@chromium.org changed reviewers:
+ sadrul@chromium.org

[jdduke (slow), 2014-08-29 15:28:50]

sadrul@: Owner review for
content/browser/renderer_host/render_widget_host_view_aura_unittest.cc? Thanks.

[sadrul, 2014-08-29 16:21:53]

lgtm

[jdduke (slow), 2014-08-29 16:25:38]

The CQ bit was checked by jdduke@chromium.org

[commit-bot: I haz the power, 2014-08-29 16:26:32]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jdduke@chromium.org/521453002/60001

[commit-bot: I haz the power, 2014-08-29 17:15:17]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[commit-bot: I haz the power, 2014-08-29 18:33:35]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-29 18:33:36]

Try jobs failed on following builders:
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[jdduke (slow), 2014-08-29 18:38:42]

The CQ bit was checked by jdduke@chromium.org

[commit-bot: I haz the power, 2014-08-29 18:39:41]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jdduke@chromium.org/521453002/60001

[commit-bot: I haz the power, 2014-08-29 22:14:24]

Committed patchset #4 (id:60001) as 3ac3c6536072a098ffa59651d06cd0b5ee55cec8

[commit-bot: I haz the power, 2014-09-10 03:10:37]

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