You need to
before you can comment on or make changes to this bug.
* W3C System Applications http://www.w3.org/wiki/System_Applications
* W3C System Application WG http://www.w3.org/2012/05/sysapps-wg-charter.html
* B2G WebBluetooth https://wiki.mozilla.org/WebAPI/WebBluetooth
* Chromium Bluetooth Extension API http://www.chromium.org/developers/design-documents/extensions/proposed-changes/apis-under-development/bluetooth-extension-api
Bluetooth Implementation on B2G https://bugzilla.mozilla.org/show_bug.cgi?id=727618
Are you going to work on adding this to WebKit? Please e-mail webkit-dev for discussion then.
I would personally strongly oppose to adding this feature to WebKit.
@Alexey, Web browsers must fallow the Web Standards and feature implementation time estimations.
As you can see Bluetooth API, Network Interface API, etc. has already LC, CR status http://www.w3.org/2012/09/sysapps-wg-charter.html
Discovery API must deliver also Bluetooth API access http://dev.webinos.org/specifications/draft/servicediscovery.html
> There is no reason to limit web applications to accessing services over WiFi, as there are many services that are either exposed directly by a device, or indirectly via USB, Firewire (IEEE 1394), Bluetooth or other interconnect technologies such as ZigBee (for sensors) and NFC. A proof of concept was developed in early 2011 as a browser plugin for mDNS, SSDP, SLP, USB and Bluetooth. This suggests that a W3C discovery and binding API should work with a range of interconnect technologies and discovery techniques.
Chrome Bluetooth API implementation: