Closed
Bug 893770
Opened 12 years ago
Closed 12 years ago
SMS Web Activity does not return to the calling app
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Firefox OS Graveyard
Gaia::SMS
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 815093
People
(Reporter: zoltanf, Unassigned)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36
Steps to reproduce:
This is somewhat similiar to #815093 but no the same. I'm a developer of a 3dt party packaged web application. I need to send an SMS from my application. I do this using Web Activity SMS as per documentation, example:
var sms = new MozActivity({
name: "new", // Possible compose-sms in future versions
data: {
type: "websms/sms",
number: "+38163123456",
body: "my test sms text"
}
});
Actual results:
When the new compose SMS activity is closed, the current focus return to the Gaia:SMS application, message list... this confuses the end user.
Expected results:
The focus should return to the 3dt party app that called the new sms web activity.
Comment 1•12 years ago
|
||
Essentially, I think you arguing that the SMS web activity should be disposition inline instead of window then, right?
I think the most logic workflow would be this:
While running a 3dt party application that needs to send an sms, user performs some action that calls the SMS Web Activity
FFOS opens the new SMS window, pre populate fields with the given info from the 3dt party web app and lets the review and change the data.
After clicking "send" or "back" (arrow in the top left corner) the new SMS window is closed and the active window is returned to the 3dt party app, the same place where the initial call to web activity was made.
....
This is not just for new SMS, this is the way generally Web Activities should perform. This is somewhat similar to other platforms, for example intents in Android. Since your security model in FFOS does not allow any other way for 3dt party apps to interact with these sensitive services, at least make it easier for user to work through this workflow.
Comment 3•12 years ago
|
||
(In reply to zoltanf from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/28.0.1500.71 Safari/537.36
>
> Steps to reproduce:
>
> This is somewhat similiar to #815093 but no the same. I'm a developer of a
> 3dt party packaged web application. I need to send an SMS from my
> application. I do this using Web Activity SMS as per documentation, example:
>
> var sms = new MozActivity({
> name: "new", // Possible compose-sms in future versions
> data: {
> type: "websms/sms",
> number: "+38163123456",
> body: "my test sms text"
> }
> });
>
>
> Actual results:
>
> When the new compose SMS activity is closed, the current focus return to the
> Gaia:SMS application, message list... this confuses the end user.
>
>
> Expected results:
>
> The focus should return to the 3dt party app that called the new sms web
> activity.
I agree with this point of view. Both, Android and iOS, open a kind of View that return to the caller Application when the operation is finished
I'm interested in work on this bug.
I guess that a good start is create a new Test Case for this kind of bug. Does Anyone confirm about this?
Comment 4•12 years ago
|
||
Comment 5•12 years ago
|
||
Julien, what do you think about this bug?
Comment 6•12 years ago
|
||
Hey Julien, did you see this bug? So what you think? I guess I can work on it.
Updated•12 years ago
|
Flags: needinfo?(felash)
Comment 7•12 years ago
|
||
I don't really know the good answer here.
Ayman, do you have an advice about comment 0 ?
Flags: needinfo?(felash) → needinfo?(aymanmaat)
Comment 8•12 years ago
|
||
I've seen bug 815093 is about the same issue and has lots of information.
It does not seem related to window/inline.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(aymanmaat)
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•12 years ago
|
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in
before you can comment on or make changes to this bug.
Description
•