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

Re: Connect Bluetooth Device

From: Rob Moran <Rob.Moran@arm.com>
Date: Thu, 3 Nov 2016 13:53:32 +0000
To: François Beaufort 🇫🇷 <fbeaufort@google.com>
CC: "public-web-bluetooth@w3.org" <public-web-bluetooth@w3.org>
Message-ID: <DB6PR0802MB2263DA21D01B2CB5A3785919E5A30@DB6PR0802MB2263.eurprd08.prod.outlook.com>

________________________________
From: François Beaufort 🇫🇷 <fbeaufort@google.com>
Sent: 03 November 2016 11:52
To: Rob Moran
Cc: David Baier; public-web-bluetooth@w3.org
Subject: Re: Connect Bluetooth Device



On Thu, Nov 3, 2016 at 10:28 AM, Rob Moran <Rob.Moran@arm.com<mailto:Rob.Moran@arm.com>> wrote:

This reminds me of a question I've been meaning to ask.


Is there a specification for a UA to populate the proposed referringDevice object?

Yes. The Web Bluetooth specification has been updated to include the refferingDevice object at https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetooth-referringdevice


Here's a public sketch as well that was used at the time: https://docs.google.com/document/d/1jFCTyq84T2fLc8ZhxorTz3u_gCk59hp17EmkFgaDQ2c/edit


[RM] Ah, this is the useful bit. Are there plans to break out the interfaces mentioned in steps 3/4 to allow Eddystone to launch other UAs or have other apps launch chrome with a referringDevice set?



I assume the first implementation will be to securely pass the device from physical web to chrome, but has any thought been given to making this device injection possible with other applications (a flag when starting chrome populated with the device handle, perhaps?). It would also allow me to specify a referringDevice in the Bleat project (perhaps as a command line switch).


Cheers,


Rob


________________________________
From: François Beaufort 🇫🇷 <fbeaufort@google.com<mailto:fbeaufort@google.com>>
Sent: 03 November 2016 08:59
To: David Baier
Cc: public-web-bluetooth@w3.org<mailto:public-web-bluetooth@w3.org>
Subject: Re: Connect Bluetooth Device

It is not yet available sadly.

Once the Permissions API is implemented, you'll be able to retrieve a BluetoothDevice instance based on a persistent ID you would have saved previously. See an example of this at https://webbluetoothcg.github.io/web-bluetooth/#example-permission-api-query




On Fri, Oct 28, 2016 at 5:51 PM, David Baier <dvdbr@live.de<mailto:dvdbr@live.de>> wrote:
Hi Community,

I just started developing with Web Bluetooth and everything works fine.
But I have one question left so far.

Is it possible to connect to a certain bluetooth device automatically?

Thanks in advance!

Kind Regards,

David



IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Received on Thursday, 3 November 2016 13:54:13 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 3 November 2016 13:54:14 UTC