connectToBluetoothServiceInsecurely should be moved to BluetoothPrivate. |
|||||||||
Issue descriptionThe API used to connect to a bluetooth device over insecure RFComm exists in the Easy Unlock API at the moment. Since this is used by other applications too and is a very generic API, we should move this to chrome.bluetoothPrivate. Since this is not supported on all platforms, we're still leaving this in chrome.bluetoothPrivate. Once this is supported on more platforms, we might consider moving it to the general API.
,
Apr 19 2016
+isherman sgtm
,
Apr 25 2016
,
Apr 25 2016
,
May 17 2016
,
Jul 13 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 5 2016
This might require the API aliasing that you're looking at Toni.
,
Apr 20 2017
Issues not modified in last 50 days aren't on track to ship in next release.
,
Jan 9 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by zelidrag@chromium.org
, Apr 18 2016