Revert of Disable swipe down to enter the tab switcher in Chrome Home.

Revert of Disable swipe down to enter the tab switcher in Chrome Home. (patchset #1 id:1 of https://codereview.chromium.org/2755823004/ )

Reason for revert:
Possibly broke multiple tests on Android concerning e.g. opening tabs.
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/40909


Original issue's description:
> Disable swipe down to enter the tab switcher in Chrome Home.
> 
> BUG=
> 
> Review-Url: https://codereview.chromium.org/2755823004
> Cr-Commit-Position: refs/heads/master@{#457836}
> Committed: https://chromium.googlesource.com/chromium/src/+/f3b96a7b630ef08149c29ffab26a70df8d54f6d8

TBR=mdjones@chromium.org,tedchoc@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

Review-Url: https://codereview.chromium.org/2761463004
Cr-Commit-Position: refs/heads/master@{#457889}
Committed: https://chromium.googlesource.com/chromium/src/+/0e89702abe2235bfb1bc778444d2eb2f166567ad

[nektarios, 2017-03-17 21:28:34]

The CQ bit was checked by nektar@chromium.org

[nektarios, 2017-03-17 21:28:34]

Created Revert of Disable swipe down to enter the tab switcher in Chrome Home.

[commit-bot: I haz the power, 2017-03-17 21:29:11]

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, 2017-03-17 21:29:56]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489786114242830, "parent_rev":
"d79ffe1a26f9a6f9572cff9c2e5f12a119032c64", "commit_rev":
"0e89702abe2235bfb1bc778444d2eb2f166567ad"}

[commit-bot: I haz the power, 2017-03-17 21:30:42]

Description was changed from

==========
Revert of Disable swipe down to enter the tab switcher in Chrome Home. (patchset
#1 id:1 of https://codereview.chromium.org/2755823004/ )

Reason for revert:
Possibly broke multiple tests on Android concerning e.g. opening tabs.
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg...


Original issue's description:
> Disable swipe down to enter the tab switcher in Chrome Home.
> 
> BUG=
> 
> Review-Url: https://codereview.chromium.org/2755823004
> Cr-Commit-Position: refs/heads/master@{#457836}
> Committed:
https://chromium.googlesource.com/chromium/src/+/f3b96a7b630ef08149c29ffab26a...

TBR=mdjones@chromium.org,tedchoc@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
==========

to

==========
Revert of Disable swipe down to enter the tab switcher in Chrome Home. (patchset
#1 id:1 of https://codereview.chromium.org/2755823004/ )

Reason for revert:
Possibly broke multiple tests on Android concerning e.g. opening tabs.
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg...


Original issue's description:
> Disable swipe down to enter the tab switcher in Chrome Home.
> 
> BUG=
> 
> Review-Url: https://codereview.chromium.org/2755823004
> Cr-Commit-Position: refs/heads/master@{#457836}
> Committed:
https://chromium.googlesource.com/chromium/src/+/f3b96a7b630ef08149c29ffab26a...

TBR=mdjones@chromium.org,tedchoc@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

Review-Url: https://codereview.chromium.org/2761463004
Cr-Commit-Position: refs/heads/master@{#457889}
Committed:
https://chromium.googlesource.com/chromium/src/+/0e89702abe2235bfb1bc778444d2...
==========

[commit-bot: I haz the power, 2017-03-17 21:30:43]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/0e89702abe2235bfb1bc778444d2...

[Ted C, 2017-03-17 23:33:50]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2755273002/ by tedchoc@chromium.org.

The reason for reverting is: Since this affects entering the tab switcher on
user gesture (and only if a chrome flag is turned on), I'm pretty sure this was
not the underlying cause.

Most likely some transient issue that caused all the devices to go offline or be
unreachable.

There was this in the logs that I got from jbudorick@
NoDevicesError: No devices attached..