The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/62ca3b416f9f385fe8d9130a3e49c162b753e8e1

commit 62ca3b416f9f385fe8d9130a3e49c162b753e8e1
Author: Olga Sharonova <olka@chromium.org>
Date: Fri May 25 12:04:08 2018

Adjusting expectation for external/wpt/css/selectors/focus-visible-002-manual.html

(flaky).

NOTRY=true
TBR=sky@chromium.org

Bug: 846656
Change-Id: I711631f169c28c525ed8ce97ae5799ca6a07adae
Reviewed-on: https://chromium-review.googlesource.com/1073410
Reviewed-by: Olga Sharonova <olka@chromium.org>
Commit-Queue: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561836}
[modify] https://crrev.com/62ca3b416f9f385fe8d9130a3e49c162b753e8e1/third_party/WebKit/LayoutTests/TestExpectations

 Issue 846603  has been merged into this issue.

Assigning to the author of the test.

Reducing priority since the test expectations has been updated.

I am going to disable this test on all platforms, because I need to land a change that turns this test from flaky to reliably failing.

I think what is happening is that the select element menu is popping up underneath the mouse cursor and stealing some of the events getting sent by mouseClickInTarget. Currently this usually works okay because in the content layer we have been locking mouseUp events to the widget surface that received the mouseDown. That behavior is wrong and I am removing it in https://chromium-review.googlesource.com/c/chromium/src/+/1099183. This test needs to be modified to not rely on the incorrect behavior.

aboxhall@ is not on CSS nor Blink at this time (to my knowledge)