For web tests this stops WindowEventDispatcher::SynthesizeMouseMoveEvent
from sending the renderer a mousemove, which it normally does on startup
and whenever we swap in a new RenderWidgetHostView.
The benefits of this change are:
- Eliminating potential flakiness by making the web tests more order-
agnostic. Tests can behave differently with the mouse at (0,0) versus
the position-unknown state which is restored in between test runs by
EventHandler::ResetLastMousePositionForWebTest. This also helps to
de-risk upcoming web test isolation changes (go/web-test-isolation).
- Aligning Windows and Linux behavior with Mac. AppKit sends a native
mousemove to a new on-screen RWHV, similar to what Aura synthesizes.
But AppKit does NOT send these mousemoves to headless web tests.
Bug: 374783343
Change-Id: I6b1d7234410cd6fa799954845bb5b50f5a2b82ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5808379
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1372147}
097916145a