Closed
Bug 1038053
Opened 10 years ago
Closed 10 years ago
Resolve stopDiscovery when adapter is not discovering
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
2.0 S6 (18july)
People
(Reporter: ben.tian, Assigned: ben.tian)
References
Details
(Whiteboard: [webbt-api])
Attachments
(1 file)
|
5.09 KB,
patch
|
echou
:
review+
|
Details | Diff | Splinter Review |
Bug 1037291's patch rejects startDiscovery when adapter is already discovering because startDiscovery returns a new discovery handle; but we should resolve stopDiscovery when adapter is not discovering since stopDiscovery returns only void.
|
Assignee | |
Updated•10 years ago
|
Assignee: nobody → btian
Whiteboard: [webbt-api]
|
|
Assignee | |
Comment 1•10 years ago
|
||
Also split startDiscovery and stopDiscovery methods.
Attachment #8455163 -
Flags: review?(echou)
|
||
Comment 2•10 years ago
|
||
Comment on attachment 8455163 [details] [diff] [review] Patch 1 (v1): Resolve stopDiscovery when adapter is not discovering Review of attachment 8455163 [details] [diff] [review]: ----------------------------------------------------------------- LGTM. Thanks!
Attachment #8455163 -
Flags: review?(echou) → review+
|
|
Assignee | |
Comment 3•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/35d873a80c26
|
||
Comment 4•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/35d873a80c26
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S6 (18july)
You need to log in
before you can comment on or make changes to this bug.
Description
•