Bug 101034 - Bluetooth API
: Bluetooth API
Status: UNCONFIRMED
Product: WebKit
Classification: Unclassified
Component: WebCore Misc.
: 528+ (Nightly build)
: All All
: P1 Major
Assigned To: Nobody
:
Depends on:
Blocks: 101162
  Show dependency treegraph
 
Reported: 2012-11-02 02:53 PDT by Binyamin
Modified: 2013-08-29 21:53 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Binyamin 2012-11-02 02:59:28 PDT
Bluetooth Implementation on B2G https://bugzilla.mozilla.org/show_bug.cgi?id=727618
Comment 2 Alexey Proskuryakov 2012-11-02 10:49:10 PDT
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.
Comment 3 Binyamin 2012-11-03 15:03:31 PDT
@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

> http://www.w3.org/QA/2011/10/web_applications_discovering_a.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.


More resources:
http://www.w3.org/2009/dap/
http://www.w3.org/Mobile/mobile-web-app-state/
http://www.w3.org/2011/04/discovery.html