Closed Bug 744705 Opened 8 years ago Closed 8 years ago

UnDOMize current bluetooth classes

Categories

(Core :: DOM: Device Interfaces, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: qdot, Assigned: qdot)

References

Details

The XPCOM objects we currently have exposed to the DOM are actually going to be used as chrome classes. Remove them from DOM exposure for the time being while we figure out what the navigator.mozBluetooth DOM should actually look like.
Adding sort-of dependency since the patch in bug 730990 is getting backed out due to wrong review chain. Will need to land again here as simple XPCOM.
Depends on: 730990
Due to the need to expose a BluetoothSocket object for implementing the file transfer profile in javascript, we'll actually be using DOM APIs for bluetooth in B2G v1 now, albeit protected by preferences that only allow them to be accessed by certain applications. This new strategy negates the need to unDOMize things. We'll just have DOM peers reviewing the bluetooth stuff (most likely bent, who's been reviewing thus far).
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Kyle, you will also need super reviews for the API.
You need to log in before you can comment on or make changes to this bug.