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

Re: [web-bluetooth] Clarify the role of requestDevice vs requestLEScan

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Fri, 05 Aug 2016 00:08:17 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-237722227-1470355694-sysbot+gh@w3.org>
Yeah, `requestDevice()` is a new kind of interface that lots of people
 won't be familiar with. We're doing it this way so that we can 
present users a choice of devices to grant access to, instead of 
making it a yes/no decision for just the device the site wants. We 
think that'll have better security properties, although we don't have 
good evidence for that yet.

We do want to add things to the chooser to make it easy to distinguish
 multiple nearby mice. We're currently adding a note in the Chrome 
chooser to identify devices that have already been paired, but I think
 we should add another one for devices that are physically connected.

GitHub Notification of comment by jyasskin
Please view or discuss this issue at 
 using your GitHub account
Received on Friday, 5 August 2016 00:11:00 UTC

This archive was generated by hypermail 2.3.1 : Friday, 5 August 2016 00:11:02 UTC