Closed
Bug 788256
Opened 12 years ago
Closed 12 years ago
[b2g-bluetooth] Expose BluetoothSockets to DOM
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 760649
People
(Reporter: qdot, Assigned: qdot)
References
Details
NOT A P1/V1 BLOCKER. This is a followup to Bug 756299. BluetoothSocket DOM object was implemented there, but is not needed since we're shifting to a manager based system for V1. However, we would like user accessible sockets at some point to move profile implementation up the chain. Most of the code is done, but needs to be OOP'd and what not.
Assignee | ||
Comment 1•12 years ago
|
||
Marking as duplicate since we really only want sockets accessible to chrome workers for the moment. Once we actually get a requirement from Product for user exposed sockets, we can open a new bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•