A bunch of tests synthesize input events during testing, and this
ranges from unit-tests, interactive-ui-tests, telemetry tests etc.
During such tests, it is possible that chrome also receives unexpected
input events from the native system (e.g. if the window happens to
show up under the mouse cursor), causing unexpected failures
(e.g. the event-stream becomes invalid, or the tooltip shows up, etc.).
Ignoring all input events from the system during these tests should
make these tests more deterministic.
PointerLockBrowserTest test suite part of content_browsertests is
affected by native mouse events.
Bug: 766450, 883710
Change-Id: Ib87043aa78f6ddd464477ad3bd42326f53a5312d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2241334
Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#777778}
6d9f24df70