Experimental change to try to reduce the flakiness of BrowserKeyEventsTest.AccessKeys
Experimental change to try to reduce the flakiness of BrowserKeyEventsTest.AccessKeys

The theory is that the QuitTask might be nestling into the message loop before the task for the result of the key press.  For example, in bug 55713, the theory is that we quit out of the message loop after the key press is sent, but before the location bar is focused.

If so, this patch should serve as a band-aid to (nearly) eliminate the test flakiness.  At that point we can try to figure out a more bulletproof fix; for now, I'd like to make sure we're right about the underlying cause of the flakiness.

BUG=55713
TEST=interactive_ui_tests --gtest_filter=BrowserKeyEventsTest.AccessKeys should not flakily fail

Review URL: http://codereview.chromium.org/3454025

git-svn-id: http://src.chromium.org/svn/trunk/src@60437 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

Former-commit-id: 1597c27aa46ec81ad21a2fdb6e6072ce45f095ae
meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser