Don't disable threaded input handling if rubberbanding is disabled.

Don't disable threaded input handling if rubberbanding is disabled.

It appears this path of code was left in for when threaded input
handling was written for OSX. It ended getting adjusted to not
be based on a command line flag but eventually on a user setting.
Since threaded input handling works correctly even though rubberbanding
is disabled ensure that we always use threaded input handling.

This was a problem because when threaded input handling isn't used
every mouse move ends up generating a post event to the main thread
and the events don't get coalesced. This isn't really a concern
because threaded input handling is always expected to be enabled.

BUG=662328
Committed: https://crrev.com/2422a4e2a7e6b13b8ab3f817912032ba16c7bd73
Cr-Commit-Position: refs/heads/master@{#431042}

[dtapuska, 2016-11-09 20:56:32]

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

[dtapuska, 2016-11-09 21:01:27]

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

[commit-bot: I haz the power, 2016-11-09 21:02:17]

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

[piman, 2016-11-09 21:05:10]

lgtm

[dtapuska, 2016-11-09 21:06:44]

The CQ bit was unchecked by dtapuska@chromium.org

[dtapuska, 2016-11-09 21:06:44]

The CQ bit was checked by dtapuska@chromium.org

[commit-bot: I haz the power, 2016-11-09 21:07:05]

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-09 21:46:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-09 21:59:41]

Description was changed from

==========
Don't disable threaded input handling if rubberbanding is disabled.

It appears this path of code was left in for when threaded input
handling was written for OSX. It ended getting adjusted to not
be based on a command line flag but eventually on a user setting.
Since threaded input handling works correctly even though rubberbanding
is disabled ensure that we always use threaded input handling.

This was a problem because when threaded input handling isn't used
every mouse move ends up generating a post event to the main thread
and the events don't get coalesced. This isn't really a concern
because threaded input handling is always expected to be enabled.

BUG=662328
==========

to

==========
Don't disable threaded input handling if rubberbanding is disabled.

It appears this path of code was left in for when threaded input
handling was written for OSX. It ended getting adjusted to not
be based on a command line flag but eventually on a user setting.
Since threaded input handling works correctly even though rubberbanding
is disabled ensure that we always use threaded input handling.

This was a problem because when threaded input handling isn't used
every mouse move ends up generating a post event to the main thread
and the events don't get coalesced. This isn't really a concern
because threaded input handling is always expected to be enabled.

BUG=662328

Committed: https://crrev.com/2422a4e2a7e6b13b8ab3f817912032ba16c7bd73
Cr-Commit-Position: refs/heads/master@{#431042}
==========

[commit-bot: I haz the power, 2016-11-09 21:59:42]

Patchset 1 (id:??) landed as
https://crrev.com/2422a4e2a7e6b13b8ab3f817912032ba16c7bd73
Cr-Commit-Position: refs/heads/master@{#431042}