device: Stop notifying observers for paired devices on Android

Instead, BluetoothAdapterAndroid updates paired devices every time
GetDevices() is called. It also updates its device cache synchronously
during the process of GetDevices() so its return value contains all
paired devices prior to the call.

It is OK not to notify observers because Web Bluetooth spec doesn't
consider paired states, and Web Serial spec requires Bluetooth devices
pairing before opening the dialog. It doesn't strictly match the API
spec of BluetoothAdapter, but it only affects rare use cases where
devices whose pairing statuses change when a chooser dialog is shown.
The notification is unreliable because it stops when the user or the
system revokes the permission.

Serial chooser also needs to remove options added by OnPortAdded() when
options are initialized, because the notification is sent by
SerialDeviceEnumerator when a port is added.

Bug: 387371131
Test: Both Bluetooth and Serial choosers look OK.
Test: device_unittests
Change-Id: I15098ae6a948af34c954b40a74f3e079a5b7905d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6341269
Reviewed-by: Jack Hsieh <chengweih@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Commit-Queue: Garfield Tan <xutan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431662}
9 files changed
tree: 8651cdc5fbc46f434708401af9f0d0b33cedb90e
  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. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  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.