Closed
Bug 878016
Opened 11 years ago
Closed 7 years ago
[WebSMS] Android backend: implement getSMSCAddress/setSMSCAddress
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: vicamo, Unassigned)
References
Details
As a follow-up for bug 859215, Android also provides APIs to get/set SMSC address.
Reporter | ||
Comment 1•11 years ago
|
||
Since bug 859215 is a WONTFIX, so is this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 2•11 years ago
|
||
Vicamo, bug 859215 has been finally fixed, do you think we would need a setSMSCAddress at one point?
Flags: needinfo?(vyang)
Reporter | ||
Comment 3•11 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #2)
> Vicamo, bug 859215 has been finally fixed, do you think we would need a
> setSMSCAddress at one point?
Julien, it depends on user stories. If we just don't have a field that allows setting a new SMSC address that differs from system default, then I don't think that's necessary. The reason bug 859215 was re-opened is you told me we need "at least" |getSmscAddress|.
Status: RESOLVED → REOPENED
Flags: needinfo?(vyang)
Resolution: WONTFIX → ---
Comment 4•11 years ago
|
||
getSmscAddress is enough to address Hermina's request, but I wonder if setSMSCAddress could be useful in the long run. It depends on user stories, but also on your personal belief :)
If you think it's not useful for now, let's close this.
Comment 5•9 years ago
|
||
Julien, do you think this is important to have for B2GDroid? I don't really know what the use cases are. If not, I think it's safe to WONTFIX this again given the lack of activity.
Flags: needinfo?(felash)
Comment 6•9 years ago
|
||
The goal is to use it in the Settings app so that the user can change its SMSC address in case it's badly configured (in the SIM or elsewhere).
Not really a priority for you, in my opinion, but not a WONTFIX either.
Flags: needinfo?(felash)
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•