Closed
Bug 401093
Opened 18 years ago
Closed 18 years ago
Do not force restart when installing unknown add-on types
Categories
(Toolkit :: Add-ons Manager, enhancement)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
FIXED
mozilla1.9beta2
People
(Reporter: jwkbugzilla, Assigned: jwkbugzilla)
References
Details
Attachments
(1 file)
1.25 KB,
patch
|
robert.strong.bugs
:
review+
mtschrep
:
approval1.9+
|
Details | Diff | Splinter Review |
ExtensionManager.installRequiresRestart() currently always returns true - unless the add-on is a theme and some special conditions are met. Unfortunately, returning true for unknown (application-defined) add-on types is a bad assumption, the restart is probably now required. I see two options:
1. Always return false for unknown add-on types and let the application itself deal with restarts.
2. Introduce a new (optional) field in install.rdf to allow overriding the restart preference.
The first option is much simpler so I would go for it unless there is a good reason to implement a different solution.
Assignee | ||
Comment 1•18 years ago
|
||
Assignee | ||
Updated•18 years ago
|
Attachment #286153 -
Flags: review? → review?(robert.bugzilla)
![]() |
||
Comment 2•18 years ago
|
||
Comment on attachment 286153 [details] [diff] [review]
Proposed patch
Good call. Thanks Wladimir
Attachment #286153 -
Flags: review?(robert.bugzilla) → review+
Updated•18 years ago
|
Attachment #286153 -
Flags: approval1.9?
Updated•18 years ago
|
Attachment #286153 -
Flags: approval1.9? → approval1.9+
Updated•18 years ago
|
Keywords: checkin-needed
Comment 3•18 years ago
|
||
Checking in toolkit/mozapps/extensions/src/nsExtensionManager.js.in;
/cvsroot/mozilla/toolkit/mozapps/extensions/src/nsExtensionManager.js.in,v <-- nsExtensionManager.js.in
new revision: 1.259; previous revision: 1.258
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3 M10
Comment 4•18 years ago
|
||
Comment on attachment 286153 [details] [diff] [review]
Proposed patch
>+ return ((type & nsIUpdateItem.TYPE_ANY) > 0);
This caused test oranges because of the missing "Ci." before "nsIUpdateItem.TYPE_ANY" (should have been Ci.nsIUpdateItem.TYPE_ANY).
Assignee | ||
Comment 5•18 years ago
|
||
Reed - thanks for fixing this. My tree didn't have bug 395311 patch, it removed the global nsIUpdateItem constant.
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•