Closed
Bug 824467
Opened 13 years ago
Closed 12 years ago
WebSMS: getThreadList always returns empty object in non-oop mode
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 849739
People
(Reporter: vicamo, Unassigned)
References
Details
Attachments
(1 file)
|
3.07 KB,
patch
|
Details | Diff | Splinter Review |
In bug 814514, we found |SmsManager.getThreadList()| works only in OOP mode by creating a simple marionette based test script. The mResult member in SmsRequest contains expected attributes as listed in SmsThreadListItem. However, the |event.target.result| got from request callback is always an empty object.
This is a serious bug for DOM API, but not for B2G because its SMS app always runs in OOP mode, so it's not affected.
|
Reporter | |
Comment 1•13 years ago
|
||
We have the same problem in bug 820780, however, we can add a '__exposedProps__' attribute in the returned object to avoid this issue. So, maybe we should do the same thing to the returned array in SmsDatabaseService.getThreadList().
You can use ObjectWrapper.jsm to fix this.
|
|
Reporter | |
Updated•13 years ago
|
Summary: WebSMS: getThreadList always returns empty object → WebSMS: getThreadList always returns empty object in non-oop mode
|
|
Reporter | |
Comment 3•12 years ago
|
||
Will be automatically fixed in bug 849739, which rewrites GetThreadList with DOMCursor.
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
•