- From: Jackson Haenchen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Apr 2018 00:17:46 +0000
- To: public-web-bluetooth-log@w3.org
@g-ortuno Do you see the issue, though for my use case? The Jabra Speak 510 is an HID that offers multiple HID usage pages. Chrome.HID, the web API I assume you refer to, will not allow interactions with keyboard and mouse usage pages but will allow other page access. For me, this is reading button pushes to start and stop the call from the input report of the Jabra. Over USB, this process works well. On Bluetooth, however, I cannot discover the HID device. I must instead go through WebBluetooth and use the HID GATT service to implement the same functionality. There is no other way as far as I can tell, to interact with these devices. I have no idea how many other hardware manufacturers use the same shortcut of HID over USB => HID over Bluetooth but it seems like an obvious approach to save time. Blocking access to the HID GATT service may prevent softphone applications from becoming fully fledged web apps. -- GitHub Notification of comment by jhaenchen Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/393#issuecomment-384826461 using your GitHub account
Received on Friday, 27 April 2018 00:17:54 UTC