Closed
Bug 783592
Opened 12 years ago
Closed 12 years ago
Wait for returnValue when an activity with href is launched
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(blocking-kilimanjaro:?, blocking-basecamp:+)
RESOLVED
INVALID
People
(Reporter: alberto.pastor, Assigned: fabrice)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.79 Safari/537.1 Steps to reproduce: Launch an activity with the href and returnValue attribute set Actual results: When executing it, it goes back to the source app without waiting for the value Expected results: Should wait until the dest app returns a value
Comment 1•12 years ago
|
||
Fabrice, is this the expected behavior? Are you the right person to fix this if so?
blocking-basecamp: --- → ?
blocking-kilimanjaro: --- → ?
Assignee | ||
Comment 2•12 years ago
|
||
According to the spec at https://wiki.mozilla.org/WebAPI/WebActivities : returnValue: the UA might want to know if the activity will return a value. For the basic activities (view, edit, etc.) the UA knows that but we need that at least for proprietary activities. This seems to be needed to be able to send a success or error event when appropriate. If an application doesn't return a value, the UA might want to send a success event as soon as an application has been picked. If a value is expected, this event will have to wait postResult() to be called. Note that UA is expected to send an error event at some point if neither postError nor postResult are called. For example, if the user leaves the application (close the tab on desktop or goes back to the homescreen on a mobile device). So yes, we can do something when returnValue == false.
Assignee: nobody → fabrice
Updated•12 years ago
|
blocking-basecamp: ? → +
Reporter | ||
Comment 3•12 years ago
|
||
It seems that returnValue was not the problem. After spending a couple of days with Fabrice looking in deep the issue, I think we have found it, and is not what this bug is describing. In my opinion, this bug can be closed and I'll file another one (which is not blocking with a gaia workaround) describing the problem.
Assignee | ||
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•