Closed
Bug 865340
Opened 13 years ago
Closed 13 years ago
Listen to new webapps-close chrome event
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
Attachments
(1 file)
Bug 844227 is going to introduce a new chrome event that is meant to close a given app. Gaia code should react accordingly to this event.
|
Assignee | |
Comment 1•13 years ago
|
||
Attachment #741411 -
Flags: review?(21)
|
|
Assignee | |
Updated•13 years ago
|
Attachment #741411 -
Flags: review?(21) → review+
|
|
Assignee | |
Comment 2•13 years ago
|
||
Comment on attachment 741411 [details]
Pull request 9387
fabrice pointed me out in bug 844227 comment 18 that we should be using manifestURL instead of origin. I updated the gaia patch accordingly.
Can you take another look and confirm that this patch is correct?
(Is origin unique per app in window manager code?)
Attachment #741411 -
Flags: review+ → review?(21)
|
||
Comment 3•13 years ago
|
||
(In reply to Alexandre Poirot (:ochameau) from comment #2)
> Comment on attachment 741411 [details]
> Pull request 9387
>
> fabrice pointed me out in bug 844227 comment 18 that we should be using
> manifestURL instead of origin. I updated the gaia patch accordingly.
> Can you take another look and confirm that this patch is correct?
> (Is origin unique per app in window manager code?)
Sadly it is 'more or less' unique. This is a long standing bug that we have not landed because of the code freeze...
Attachment #741411 -
Flags: review?(21) → review+
|
|
Assignee | |
Comment 4•13 years ago
|
||
Landed in:
master: 42ca2b7eed8ef3aa35eca0c4ac021658c4df8199
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•