Remove is_fling flag for fling intervention

In the previous patch, https://codereview.chromium.org/1923973002/, we added a is_fling flag
to indicate if the active fling is happening on either main or impl thread.

Now we only consider about scrolling happening in impl thread and we will use ack states to
indicate if we want to make the touch events uncancelable.

BUG=595327
Committed: https://crrev.com/8f1957b19f5c0e8e09dc98480c613e2e5c59cd99
Cr-Commit-Position: refs/heads/master@{#430640}

[lanwei, 2016-11-06 21:57:02]

The CQ bit was checked by lanwei@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-06 21:57:05]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[lanwei, 2016-11-06 22:05:05]

Description was changed from

==========
remove flag


 fling layer

BUG=
==========

to

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states to indicate
if we want to make the touch events uncancelable.

BUG=595327
==========

[lanwei, 2016-11-06 22:05:06]

lanwei@chromium.org changed reviewers:
+ tdresser@chromium.org

[lanwei, 2016-11-06 22:06:05]

Description was changed from

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states to indicate
if we want to make the touch events uncancelable.

BUG=595327
==========

to

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states
to indicate if we want to make the touch events uncancelable.

BUG=595327
==========

[lanwei, 2016-11-06 22:06:26]

Description was changed from

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states
to indicate if we want to make the touch events uncancelable.

BUG=595327
==========

to

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states to
indicate if we want to make the touch events uncancelable.

BUG=595327
==========

[commit-bot: I haz the power, 2016-11-06 22:11:05]

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

[commit-bot: I haz the power, 2016-11-06 22:11:06]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[lanwei, 2016-11-06 22:48:06]

The CQ bit was checked by lanwei@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-06 22:48:17]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[lanwei, 2016-11-06 22:53:08]

Patchset #1 (id:1) has been deleted

[commit-bot: I haz the power, 2016-11-06 23:53:49]

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

[commit-bot: I haz the power, 2016-11-06 23:53:50]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[tdresser, 2016-11-07 17:57:31]

tdresser@chromium.org changed reviewers:
+ dtapuska@chromium.org

[tdresser, 2016-11-07 17:57:31]

https://codereview.chromium.org/2479023003/diff/20001/content/common/input/in...
File content/common/input/input_event_ack_state.h (right):

https://codereview.chromium.org/2479023003/diff/20001/content/common/input/in...
content/common/input/input_event_ack_state.h:15:
INPUT_EVENT_ACK_STATE_NOT_CONSUMED_NON_BLOCKING,
Should this be NOT_CONSUMED_SET_NON_BLOCKING?
Could we just use SET_NON_BLOCKING?

[lanwei, 2016-11-07 20:20:05]

The CQ bit was checked by lanwei@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-07 20:20:38]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[tdresser, 2016-11-07 21:58:49]

LGTM.

https://codereview.chromium.org/2479023003/diff/40001/content/renderer/input/...
File content/renderer/input/input_event_filter.cc (right):

https://codereview.chromium.org/2479023003/diff/40001/content/renderer/input/...
content/renderer/input/input_event_filter.cc:241: ack_state ==
INPUT_EVENT_ACK_STATE_SET_NON_BLOCKING_DUE_TO_FLING) {
Nit: might be nice to reorder these such that the set_non_blocking's are
contiguous.

[lanwei, 2016-11-07 22:08:29]

lanwei@chromium.org changed reviewers:
+ avi@chromium.org, tkent@chromium.org, wez@chromium.org

[lanwei, 2016-11-07 22:08:29]

wez@chromium.org: Please review changes in 
blimp/

avi@chromium.org: Please review changes in 
content/renderer/

tkent@chromium.org: Please review changes in 
 third_party/WebKit/

Thank you!

[Wez, 2016-11-07 22:54:07]

https://codereview.chromium.org/2479023003/diff/40001/blimp/client/core/input...
File blimp/client/core/input/blimp_input_handler_wrapper.cc (right):

https://codereview.chromium.org/2479023003/diff/40001/blimp/client/core/input...
blimp/client/core/input/blimp_input_handler_wrapper.cc:74: default:
This should explicitly catch the new enum, rather than using default.

[lanwei, 2016-11-07 23:21:47]

The CQ bit was checked by lanwei@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-07 23:22:22]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[lanwei, 2016-11-07 23:25:18]

https://codereview.chromium.org/2479023003/diff/40001/blimp/client/core/input...
File blimp/client/core/input/blimp_input_handler_wrapper.cc (right):

https://codereview.chromium.org/2479023003/diff/40001/blimp/client/core/input...
blimp/client/core/input/blimp_input_handler_wrapper.cc:74: default:
On 2016/11/07 22:54:07, Wez wrote:
> This should explicitly catch the new enum, rather than using default.

Done.

https://codereview.chromium.org/2479023003/diff/40001/content/renderer/input/...
File content/renderer/input/input_event_filter.cc (right):

https://codereview.chromium.org/2479023003/diff/40001/content/renderer/input/...
content/renderer/input/input_event_filter.cc:241: ack_state ==
INPUT_EVENT_ACK_STATE_SET_NON_BLOCKING_DUE_TO_FLING) {
On 2016/11/07 21:58:49, tdresser wrote:
> Nit: might be nice to reorder these such that the set_non_blocking's are
> contiguous.

Done.

[Wez, 2016-11-07 23:34:33]

Perfect - thanks. :)

LGTM

[commit-bot: I haz the power, 2016-11-08 01:05:06]

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

[commit-bot: I haz the power, 2016-11-08 01:05:07]

Dry run: This issue passed the CQ dry run.

[tkent, 2016-11-08 01:32:46]

> tkent@chromium.org: Please review changes in 
>  third_party/WebKit/


lgtm

[lanwei, 2016-11-08 03:19:42]

lanwei@chromium.org changed reviewers:
- avi@chromium.org

[lanwei, 2016-11-08 03:22:29]

lanwei@chromium.org changed reviewers:
+ avi@chromium.org

[Avi (use Gerrit), 2016-11-08 16:23:49]

content lgtm

[dtapuska, 2016-11-08 17:01:21]

On 2016/11/08 16:23:49, Avi wrote:
> content lgtm

lgtm

[lanwei, 2016-11-08 17:03:38]

The CQ bit was checked by lanwei@chromium.org

[lanwei, 2016-11-08 17:03:39]

The patchset sent to the CQ was uploaded after l-g-t-m from
tdresser@chromium.org
Link to the patchset: https://codereview.chromium.org/2479023003/#ps60001
(title: "Make enum explicitly")

[commit-bot: I haz the power, 2016-11-08 17:03:59]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-08 17:09:56]

Description was changed from

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states to
indicate if we want to make the touch events uncancelable.

BUG=595327
==========

to

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states to
indicate if we want to make the touch events uncancelable.

BUG=595327
==========

[commit-bot: I haz the power, 2016-11-08 17:09:59]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2016-11-08 17:16:24]

Description was changed from

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread. 

Now we only consider about scrolling happening in impl thread and we will use
ack states to
indicate if we want to make the touch events uncancelable.

BUG=595327
==========

to

==========
In the previous patch, https://codereview.chromium.org/1923973002/, we added a
is_fling flag
to indicate if the active fling is happening on either main or impl thread.

Now we only consider about scrolling happening in impl thread and we will use
ack states to
indicate if we want to make the touch events uncancelable.

BUG=595327

Committed: https://crrev.com/8f1957b19f5c0e8e09dc98480c613e2e5c59cd99
Cr-Commit-Position: refs/heads/master@{#430640}
==========

[commit-bot: I haz the power, 2016-11-08 17:16:26]

Patchset 3 (id:??) landed as
https://crrev.com/8f1957b19f5c0e8e09dc98480c613e2e5c59cd99
Cr-Commit-Position: refs/heads/master@{#430640}