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

Re: Dropping the device-info fields from BluetoothDevice

From: Rob Moran <Rob.Moran@arm.com>
Date: Sat, 16 Apr 2016 05:49:07 +0000
To: Jeffrey Yasskin <jyasskin@google.com>
CC: public-web-bluetooth <public-web-bluetooth@w3.org>
Message-ID: <aad7173b-7096-4664-afb9-19b438ed1372@email.android.com>
Sounds sensible

Hi all,

I'm strongly considering dropping the 4 fields from BluetoothDevice
that are populated from the Device Info service: vendorIDSource,
vendorID, productID, and productVersion (and maybe deviceClass while
I'm at it). They're holdovers from copying the interface from
chrome.bluetooth.Device and don't exist on Android
or CoreBluetooth
Folks will still be able to explicitly navigate the GATT tree to read
those fields.

They're also the only thing that requires connecting to the device
while the UA's creating a BluetoothDevice instance
and the resulting asynchrony is causing a small problem specifying the
navigator.bluetooth.referringDevice field in
This could be solved by moving the referring device inside the result
of navigator.permissions.query({"bluetooth"}), but if we can get rid
of the fields, that's easier.

Any objections?


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 Saturday, 16 April 2016 05:49:35 UTC

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