Hugo, could you take this?

I got a little confused when looking at the test result page. I see two flaky snav tests, neither is snav-overlapping-elements.html. They both happen on Windows 10 only.

1. fast/spatial-navigation/snav-not-rightof.html @
 - https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win10/builds/24428
 - https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win10/builds/24378

2. fast/spatial-navigation/snav-symmetrically-positioned.html @
  https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win10/builds/24412

When looking at snav-not-rightof-actual.txt I see:

PASS gFocusedDocument.activeElement.getAttribute("id") is "e1"
FAIL gFocusedDocument.activeElement.getAttribute("id") should be e2. Was e1.
FAIL gFocusedDocument.activeElement.getAttribute("id") should be e2. Was e1.
FAIL gFocusedDocument.activeElement.getAttribute("id") should be e3. Was e2.
FAIL gFocusedDocument.activeElement.getAttribute("id") should be e3. Was e2.
FAIL gFocusedDocument.activeElement.getAttribute("id") should be e2. Was e1.
FAIL gFocusedDocument.activeElement.getAttribute("id") should be e2. Was e1.
PASS gFocusedDocument.activeElement.getAttribute("id") is "e1"

Focus moved correctly except at the first Down key (focus stayed in e1 so the remaining asserts fail as well).
Also snav-symmetrically-positioned-actual.txt indicates the first Down key stroke went missing.

Is "missing" key strokes on Windows a known cause for flakiness? Even tough the test runs on 'onload', my guess is that content_shell (sometimes -> flake) hasn't yet started up properly so the first Down stroke goes missing somewhere. This is tricky for me to debug because I only have a Linux workstation. Maybe someone who knows the Win10 test environment better could take this?

 Issue 774688  has been merged into this issue.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot