tree: d5fad9977b271974c2c9f2fa00b26fc51c1ce346 [path history] [tgz]
  1. testing/
  2. Bluetooth.cpp
  3. Bluetooth.h
  4. Bluetooth.idl
  5. BluetoothAttributeInstanceMap.cpp
  6. BluetoothAttributeInstanceMap.h
  7. BluetoothCharacteristicProperties.cpp
  8. BluetoothCharacteristicProperties.h
  9. BluetoothCharacteristicProperties.idl
  10. BluetoothDevice.cpp
  11. BluetoothDevice.h
  12. BluetoothDevice.idl
  13. BluetoothError.cpp
  14. BluetoothError.h
  15. BluetoothRemoteGATTCharacteristic.cpp
  16. BluetoothRemoteGATTCharacteristic.h
  17. BluetoothRemoteGATTCharacteristic.idl
  18. BluetoothRemoteGATTServer.cpp
  19. BluetoothRemoteGATTServer.h
  20. BluetoothRemoteGATTServer.idl
  21. BluetoothRemoteGATTService.cpp
  22. BluetoothRemoteGATTService.h
  23. BluetoothRemoteGATTService.idl
  24. BluetoothScanFilterInit.idl
  25. BluetoothSupplement.cpp
  26. BluetoothSupplement.h
  27. BluetoothUUID.cpp
  28. BluetoothUUID.h
  29. BluetoothUUID.idl
  30. BUILD.gn
  31. DEPS
  32. NavigatorBluetooth.cpp
  33. NavigatorBluetooth.h
  34. NavigatorBluetooth.idl
  35. OWNERS
  36. README.md
  37. RequestDeviceOptions.idl
third_party/WebKit/Source/modules/bluetooth/README.md

Web Bluetooth

Source/modules/bluetooth implements Web Bluetooth.

Scanning

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.

Testing

Bluetooth layout tests in LayoutTests/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 API layer.

Design Documents

See: Class Diagram of Web Bluetooth through Bluetooth Android