W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > May 2016

[web-bluetooth] requestDevice() not considering already connected devices

From: Martijn Thé via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 May 2016 14:15:53 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issues.opened-153022773-1462371352-sysbot+gh@w3.org>
martijnthe has just created a new issue for 
https://github.com/WebBluetoothCG/web-bluetooth:

== requestDevice() not considering already connected devices ==
A device could already be connected to the machine that the UA runs 
on, prior to the `requestDevice()` call. When a connection is 
established, devices often stop advertising, so won't get found by 
scanning and won't be "found" by `requestDevice()`.

A connection could have been established, prior to the 
`requestDevice()` call, for various reasons:
- if another site has already connected to it,
- the platform or another app running on it connected to it,
- the device connected to the machine that the UA runs on (in case the
 machine was acting as a peripheral at the same time).

Looking at the [steps that the UA has to 
take](https://webbluetoothcg.github.io/web-bluetooth/#ref-for-dom-bluetooth-requestdevice-3)
 for `requestDevice()`, it seems that already-connected, 
non-advertising devices are ignored and will not be shown in the list.
 I think the UA should also match already-connected devices, using the
 GATT cache and possibly also the last known advertisement data to 
match.

Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/issues/237 using your 
GitHub account
Received on Wednesday, 4 May 2016 14:15:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 May 2016 14:15:56 UTC