Google Git
Sign in
chromium / chromium / src / a60d4be9a5a534bcf70fda407dae08e998807175
commita60d4be9a5a534bcf70fda407dae08e998807175[log] [tgz]
authorGordon Seto <gordonseto@google.com>Fri Jun 03 23:06:25 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 03 23:06:25 2022
tree34b14ac3f70546c9fd29870a0c8c7e472031ed7b
parent21a99b48ea1a50a2872d1b54a651b514da87e46f [diff]
[CrOS Bluetooth] Close all mojo connections when pairing dialog closes.

Update <bluetooth-pairing-ui> to close all Mojo connections when it
is removed from the DOM. Previously, it would not do so, so if it is
removed from the DOM and Bluetooth is disabled, then re-enabled, it will
automatically start discovery because it is still observing
CrosBluetoothConfig properties. In some cases, this behavior can cause
Bluetooth to automatically re-enable after being disabled.

Recording: https://drive.google.com/file/d/1sIuCT-NLAurxRd22asYq_qlobOCO_kOy/view?usp=sharing

(cherry picked from commit cbf51ee52e54d3c02c24e24d598f8ca525289bf6)

Fixed: b/231738454
Change-Id: I51183eacdb9b0294d3de79d92075fa5f23345835
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3669998
Reviewed-by: Chad Duffin <chadduffin@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Chad Duffin <chadduffin@chromium.org>
Auto-Submit: Gordon Seto <gordonseto@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1008266}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3689704
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5060@{#531}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
3 files changed
tree: 34b14ac3f70546c9fd29870a0c8c7e472031ed7b
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.