Re: [web-bluetooth] Discover "non-discoverable" beacons

APIs that scan for devices, like Android's and iOS's, may just be 
doing a non-standardized procedure, rather than than the standardized 
General Discovery procedure. Right now, the WebBT spec requires 
`requestDevice()` to do the standardized procedure, but it'd be 
straightforward to specify something else that ignores the 
Discoverable bits. I haven't yet figured out which behavior I prefer.

Nordic may just be working around a hole in the Android API: Android 
[provides the 
 but not whether the AD packet was connectable. iOS, on the other 
hand, [provides whether the packet was 
 but not the flags.

GitHub Notif of comment by jyasskin

Received on Monday, 20 July 2015 23:38:54 UTC