- From: Vincent Scheib via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Mar 2016 15:31:28 +0000
- To: public-web-bluetooth-log@w3.org
... and the reason Chrome does not attempt to be backwards compatible and use multiple APIs is because M is the first version that allows runtime permission requests. Older versions of android would block users from updating Chrome without accepting a new up-front Bluetooth permission -- and any upgrade friction to Chrome is a security risk for users. On Fri, Mar 25, 2016 at 7:52 AM, Giovanni Ortuno <notifications@github.com> wrote: > Yes. KitKat is not supported. The BLE APIs in KitKat are different than > the APIs in L and M, which are the APIs Web Bluetooth uses. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub > <https://github.com/WebBluetoothCG/web-bluetooth/issues/224#issuecomment-201320885> > -- GitHub Notification of comment by scheib Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/224#issuecomment-201333710 using your GitHub account
Received on Friday, 25 March 2016 15:31:29 UTC