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

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

From: Julien Racle via GitHub <sysbot+gh@w3.org>
Date: Fri, 05 Aug 2016 07:21:15 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-237775043-1470381674-sysbot+gh@w3.org>
> Yeah, requestDevice() is a new kind of interface that lots of people
 won't be familiar with. 

That's my fear :).

> 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.

What prevents us to show a (different) chooser twice (when requesting 
connected peripherals and when scanning)?

> ..., but I think we should add another one for devices that are 
physically connected.

Yes, that's indeed needed when choosing my mouse and not my 
neighbors'.

-- 
GitHub Notification of comment by jracle
Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/issues/255#issuecomment-237775043
 using your GitHub account
Received on Friday, 5 August 2016 07:23:20 UTC

This archive was generated by hypermail 2.3.1 : Friday, 5 August 2016 07:23:20 UTC