- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Apr 2018 17:48:37 +0000
- To: public-web-bluetooth-log@w3.org
chrome.hid is not a web API since it is restricted to Chrome Apps and predates WebUSB by years so it isn't an implementation of the first approach [there](https://github.com/WICG/webusb/issues/29#issuecomment-274623755). To my knowledge there has been no movement on the second approach. The third approach is what I recommend to developers building devices they intend on using with WebUSB. It's unfortunate that the work to make chrome.hid work reliably with Bluetooth devices was never done. To be clear, what would need to be done to Web Bluetooth to unblock the HID GATT service is to implement support for parsing the HID messages encoded in GATT messages and applying similar filtering to what is done in the chrome.hid API. This behavior would need to be carefully specified so that it could be implemented consistently across browsers. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/393#issuecomment-385475562 using your GitHub account
Received on Monday, 30 April 2018 17:48:40 UTC