Google Git
Sign in
chromium / chromium / src / bb463f964c9ae7a095359f3db00ab2d14909a325
commitbb463f964c9ae7a095359f3db00ab2d14909a325[log] [tgz]
authorAman Verma <amanvr@google.com>Fri May 30 14:39:05 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 30 14:39:05 2025
treed9e5b0d161f633d37cc908e58c62b5bfa44992a0
parent9edaed2b1c1d6e4acaf52e244d7fee8b9e1fdb15 [diff]
[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}
7 files changed
tree: d9e5b0d161f633d37cc908e58c62b5bfa44992a0
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. internal
  52. ios_internal
  53. native_client
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .git-blame-ignore-revs
  60. .gitallowed
  61. .gitattributes
  62. .gitignore
  63. .gitmodules
  64. .gn
  65. .mailmap
  66. .rustfmt.toml
  67. .vpython3
  68. .yapfignore
  69. ATL_OWNERS
  70. AUTHORS
  71. BUILD.gn
  72. CODE_OF_CONDUCT.md
  73. codereview.settings
  74. CPPLINT.cfg
  75. CRYPTO_OWNERS
  76. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. SECURITY_OWNERS
  86. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.