Source/modules/bluetooth implements the renderer process details and bindings for the Web Bluetooth specification. It uses the Web Bluetooth Service mojom to communicate with the Web Bluetooth Service.
There isn't much support for GATT over BR/EDR from neither platforms nor devices so performing a Dual scan will find devices that the API is not able to interact with. To avoid wasting power and confusing users with devices they are not able to interact with, navigator.bluetooth.requestDevice performs an LE-only Scan.
Web Bluetooth implementation details are tested at several layers:
/device/bluetooth/*_unittest.ccdevice_unittests --gtest_filter="*Bluetooth*"/chrome/browser/*bluetooth*_browsertest.ccout/Release/browser_tests --gtest_filter="*Bluetooth*"/content/*/bluetooth/*_unittest.ccout/Release/content_unittests --gtest_filter="*Bluetooth*"LayoutTests/bluetooth/*/*.htmlblink/tools/run_layout_tests.sh bluetoothLayoutTests/bluetooth/ rely on fake Bluetooth implementation classes constructed in content/shell/browser/layout_test/layout_test_bluetooth_adapter_provider. These tests span JavaScript binding to the device/bluetooth platform abstraction layer.testing/clusterfuzzSee: Class Diagram of Web Bluetooth through Bluetooth Android