tree d9e5b0d161f633d37cc908e58c62b5bfa44992a0
parent 9edaed2b1c1d6e4acaf52e244d7fee8b9e1fdb15
author Aman Verma <amanvr@google.com> 1748615945 -0700
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1748615945 -0700

[InputVizard] Check RIRDelegate mojo connection setup before
transferring input to VizCompositorThread.

This change adds a check to ensure that the mojo connection is setup
between RenderWidgetHostImpl (in the browser process) and InputManager
(on the VizCompositorThread) to allow transferring input to Viz for
handling with InputVizard.

If the connection is not yet set up, the input transfer will be
prevented, and the event sequence will be handled by the browser process
instead.  This prevents potential issues or unexpected behavior when
input is transferred before the necessary communication channels are
ready. Currently, this case is captured in
"Android.InputOnViz.Viz.StateProcessingResult" histogram under
`kCouldNotFindViewForFrameSinkId` enum and the input sequence is dropped
by Viz, but with this change it would be handled on the browser itself.

Bug: 420888292, 383323530
Change-Id: I27463b60a73e3032935e03421ccebf9ce33830f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6603033
Commit-Queue: Aman Verma <amanvr@google.com>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Ashley Newson <ashleynewson@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1467467}