- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 May 2018 18:15:14 +0000
- To: public-web-bluetooth-log@w3.org
The specification contains the following in the steps for [BluetoothRemoteGATTServer.connect()](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothremotegattserver-connect), > Note: We would normally prefer to give the website control over whether and when bonding happens, but the Core Bluetooth platform API doesn’t provide a way for UAs to implement such a knob. Having a bond is more secure than not having one, so this specification allows the UA to opportunistically create one on platforms where that’s possible. This may cause a user-visible pairing dialog to appear when a connection is created, instead of when a restricted characteristic is accessed. This implies that if the device requires pairing using a PIN code then the user will be prompted for this code when the site attempts to connect to the device. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/397#issuecomment-392139401 using your GitHub account
Received on Friday, 25 May 2018 18:15:16 UTC