Issue 707919 has been merged into this issue.

Looking at history on wmatrix, this test last passed on build 9389.0.0 and has been failing since 9391.0.0.

- Ran test on local DUT
- Tried to manually press the back/forward/refresh keys during autotest. No response.
- Tried to manually press the other functional keys during autotest period (brightness, volume, etc.) These got immediate response. 
- No issue with manually logging in and using back/forward/refresh keys.

Seems like it's an autotest issue? 
I also looked at the diffs between the two builds and couldn't find anything that looked relevant. 

Sounds like a test issue, not an infra issue. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/82d0b5904f814845e43c8b388d8dfca9ac5a4fb2

commit 82d0b5904f814845e43c8b388d8dfca9ac5a4fb2
Author: Ruchi Jahagirdar <rjahagir@google.com>
Date: Fri Apr 28 09:58:14 2017

[Autotest] Removing platform_InputBrowserNav

Removing platform_InputBrowserNav from platform_input suite due to
repeated failures. Will revert once bug has been fixed.

BUG= chromium:705589 
TEST=None

Change-Id: I003f69418f2588b3744953ba00a018fb489818c2
Reviewed-on: https://chromium-review.googlesource.com/489667
Commit-Ready: Ruchi Jahagirdar <rjahagir@chromium.org>
Tested-by: Ruchi Jahagirdar <rjahagir@chromium.org>
Reviewed-by: Kalin Stoyanov <kalin@chromium.org>

[modify] https://crrev.com/82d0b5904f814845e43c8b388d8dfca9ac5a4fb2/client/site_tests/platform_InputBrowserNav/control