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 09:28:04 +0000
To: David Baier <dvdbr@live.de>, "public-web-bluetooth@w3.org" <public-web-bluetooth@w3.org>
CC: François Beaufort 🇫🇷 <fbeaufort@google.com>
Message-ID: <DB6PR0802MB226390E12B395F55C8961787E5A30@DB6PR0802MB2263.eurprd08.prod.outlook.com>
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?

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



From: François Beaufort 🇫🇷 <fbeaufort@google.com>
Sent: 03 November 2016 08:59
To: David Baier
Cc: 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,


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 09:28:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:55 UTC