Reland "[CrOS Bluetooth] Add HidDisconnected metric HID detection screen." This reverts commit 2680c70e34d1d7b3beb305bc638626a46fb6bf06. Reason for revert: Fix crash caused by device key not existing when recording a disconnect. Empirically, it was found that when a device is removed, several other devices are also removed from input_device_manager that were not originally registered as added by HIDDetectionScreen. These devices would cause a crash because they would not be present in the devices map. This CL fixes this by checking if the device is found in the map before recording the disconnect. Original change's description: > [CrOS Bluetooth] Add HidDisconnected metric HID detection screen. > > Add a RecordHidDisconnected member to the hid_detection_utils.h > class to record when a HID has been disconnected. Emit > HidDisconnected histogram metric for each HID disconnected while > the HID detection screen is shown. Add a test > AddRemoveDevicesAfterScreen to make sure HidConnected and > HidDisconnected are not recorded outside of the HID detection > screen. Change-Id: I41e5f9057b794d225fabe98d14104435ef1c51a5 Fixed: b/235083051 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3718443 Commit-Queue: Andrew Dear <andrewdear@google.com> Reviewed-by: Gordon Seto <gordonseto@google.com> Reviewed-by: Roman Sorokin <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026372}
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.