Google Git
Sign in
chromium / chromium / src / 4f3648603a22f2fdccd1732cd1a1bce7003bc90f
commit4f3648603a22f2fdccd1732cd1a1bce7003bc90f[log] [tgz]
authorXiyuan Xia <xiyuan@chromium.org>Fri Jun 27 18:21:59 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 27 18:21:59 2025
treefe6a4ed07ce9b7e27f6464b0de8a868dc68a85eb
parentfba0504478a1c27a243bde282102fec337fa6b9f [diff]
[Accessibility Common] Share message processing

Ensure only one chrome.runtime.onMessage listener exists in
the offscreen document. Route incoming messages to appropriate handlers
to maintain modular logic.

In Chrome extension messaging, only the first registered onMessage
listener is invoked. If it returns false or nothing and doesn’t call
sendResponse synchronously, Chrome treats the message as handled and
closes the port. This affects both synchronous and asynchronous
messages, and can lead to the error: "The message port closed before a
response was received." To avoid dropped responses and ensure consistent
behavior, message handling should be centralized.

Changes on top of crrev.com/c/6563668:
- Move message handling into `Messenger` so that service worker side
  could share message processing too.

AX-Relnotes: n/a.
Bug: 388867838
Change-Id: I1f2146a307e331be74693e37948f83029dd75124
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6680169
Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1479963}
6 files changed
tree: fe6a4ed07ce9b7e27f6464b0de8a868dc68a85eb
  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. 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. signing_keys
  53. v8
  54. .clang-format
  55. .clang-tidy
  56. .clangd
  57. .cursorignore
  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.