Deflake CustomLauncherPageBrowserTest.EventsActivateSwitchToCustomPage on ChromeOS Buildspec Tests

Deflake CustomLauncherPageBrowserTest.EventsActivateSwitchToCustomPage on ChromeOS Buildspec Tests

The failure doesn't reproduce with --enable-pixel-output-in-tests, so I
don't really know what's going on. But I suspect that since ChromeOS
only checks the *target* visibility, it's possible for the app list to
not be fully shown.

One case this could happen is on official/buildspec builders which
have more icons to load, and so the delayed-icon-load steps used
for ChromeOS via AppListMainView::ShowAppListWhenReady() end up
taking longer.

Explicitly showing the app list ensures the app list is visible
before the event generator tries to use it to generate mouse coordinates.

BUG=525128
Committed: https://crrev.com/2e95c57b25f079105d3b822f3bc1de226bc3bbaa
Cr-Commit-Position: refs/heads/master@{#347886}

[tapted, 2015-09-09 05:32:36]

tapted@chromium.org changed reviewers:
+ calamity@chromium.org

[tapted, 2015-09-09 05:32:36]

Hi Chris - please take a look

[calamity, 2015-09-09 07:09:16]

lgtm

[tapted, 2015-09-09 07:09:58]

The CQ bit was checked by tapted@chromium.org

[commit-bot: I haz the power, 2015-09-09 07:11:00]

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

[commit-bot: I haz the power, 2015-09-09 09:17:05]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-09-09 09:18:12]

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