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

Removing GAP and GATT services from the blacklist

From: Jeffrey Yasskin <jyasskin@google.com>
Date: Tue, 9 Feb 2016 14:00:18 -0800
Message-ID: <CANh-dXn0AFx_i280azoN8uLr-Se2GquTtznL-h1+t4Qohwo6TA@mail.gmail.com>
To: public-web-bluetooth <public-web-bluetooth@w3.org>
I've sent https://github.com/WebBluetoothCG/registries/pull/5 to allow
access to the GAP and GATT services. The change blocks writes to
the peripheral_privacy_flag and all access to the reconnection_address

Until we either change BlueZ or emulate the services, ChromeOS still won't
allow access, but I'm told that Android does allow it.

Does anyone think this is the wrong direction, or that we need to blacklist
a different set of characteristics?

Please discuss on the pull request so there's just one thread.

Received on Tuesday, 9 February 2016 22:01:06 UTC

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