Closed
Bug 790495
Opened 13 years ago
Closed 13 years ago
Webapps.jsm doesn't call _registerActivities when installing a new app
Categories
(Core Graveyard :: DOM: Apps, defect)
Tracking
(blocking-basecamp:-)
RESOLVED
INVALID
blocking-basecamp | - |
People
(Reporter: dhylands, Unassigned)
Details
I noticed that init calls _processManifestForId which in turn does:
app.name = manifest.name;
this._registerSystemMessages(manifest, app);
this._registerActivities(manifest, app);
however, when installing an app (in confirmInstall) it doesn't call _registerSystemMessages anywhere.
In fact it might make sense to factor the 3 lines mentioned above into a function? Right now, it's doing
appObject.name = app.manifest.name;
(this has to happen on appObject which the instance stored in this.webapps[id]). It isn't clear to me whether _registerSystemMessage and _registerActivities need to be called on app or whether it will work just as well on appObject.
Updated•13 years ago
|
blocking-basecamp: --- → ?
Comment 1•13 years ago
|
||
_registerSystemMessages() is called in confirmInstall, but not _registerActivities().
I added the call in my local patch for bug 788125. I'll probably also refactor confirmInstall() when working on bug 789527.
Comment 2•13 years ago
|
||
Not blocking based on comment #1 and Fabrice's other work.
blocking-basecamp: ? → -
Reporter | ||
Comment 3•13 years ago
|
||
I wasn't sure if Fabrice had a bug already. So I'll go ahead and resolve this one.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•