- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jul 2015 11:50:52 +0000
- To: public-web-bluetooth-log@w3.org
I believe `navigator.bluetooth.requestDevice` UA chooser should be the one responsible for communicating to the user the state of the Bluetooth Adapter: - Bluetooth adapter doesn't exist. In that case rejects instantly properly the promise with some `BluetoothAdapterNotFoundError` error. Regarding privacy concern, it might be hard to avoid timing attacks there. - Bluetooth adapter is off. "Turn on Bluetooth" should be available right there in the chooser if possible and would trigger a new BT search when enabled. If user dismisses it, the promise would be rejected with some `BluetoothAdapterNotFoundError` error. -- GitHub Notif of comment by beaufortfrancois See https://github.com/WebBluetoothCG/web-bluetooth/issues/127#issuecomment-119548843
Received on Wednesday, 8 July 2015 11:50:53 UTC