Hi Lars, Web Bluetooth is behind a flag in M48 and we are rebasing Crosswalk to M48 now.
Chrome will not enable Web Bluetooth on non-M versions of Android, given that it would require users to accept additional permissions when upgrading Chrome, but we don't have that problem. As it is behind a flag, whether we enable it earlier depends on a few things, like - the risk that the feature affects the stability for people not using Web Bluetooth - that users understand that the API is experimental and some changes might happen in later xwalk versions - how well the current implementation of Web Bluetooth on Android actually works and whether it works well on non-M Android versions as well. Could you as a user of Web Bluetooth live with the above points? ie, that the API might change a bit in future versions? Maybe we can publish some info on how to build the next version of XWalk with Web Bluetooth enabled or make a few additional builds Cheers Kenneth On Tue, Jan 19, 2016 at 4:56 PM Lars Knudsen <[email protected]> wrote: > Hi guys, > > we would REALLY like to see WebBluetooth working through xwalk when M48 > gets done. Currently, our only other option is to use cordova with plugins > or hacking some extension under xwalk ourselves. > > Can someone give me a hint on when WebBluetooth should be available? > > br > Lars Knudsen > _______________________________________________ > Crosswalk-help mailing list > [email protected] > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help >
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
