Google Git
Sign in
chromium / chromium / src / 2e7b98dac8a63f59c173159251c3bcbf2d56ba80
commit2e7b98dac8a63f59c173159251c3bcbf2d56ba80[log] [tgz]
authorMaria Kazinova <kazinova@google.com>Fri May 16 14:20:15 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 16 14:20:15 2025
treeaa7c8c1f47d2ff20009c91a3304fbc0171288cb0
parent12c3674b3a3a62eebbd1a2d36ca7f4871b76a806 [diff]
[OTPs] Add the dispatcher bridge for Android SMS OTP fetcher.

The communication between native and Java OTP filling code will
happen via 2 bridges.
1) One (dispatcher, implemented in this CL) will send requests to
the Java side
2) Another one (receiver, already landed) will propagate the replies
back.

There isn't a single bridge, because sending requests and receiving
replies from the downstream Java OTP fetcher has to happen on
different threads, so we need 2 different objects (since one object
should not live on 2 threads).
This is needed to avoid loading the main thread with posting an OTP
fetch request on the pageload (so it should happen on the background
thread to not hinder performance), but the replies will be posted on
the main UI thread by the downstream implementation.

Bug: 415271020
Change-Id: I4e1879502d486146219be5b7babecca7025d9597
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6553125
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Commit-Queue: Maria Kazinova <kazinova@google.com>
Cr-Commit-Position: refs/heads/main@{#1461331}
9 files changed
tree: aa7c8c1f47d2ff20009c91a3304fbc0171288cb0
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. SECURITY_OWNERS
  85. 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.