Closed
Bug 572049
Opened 15 years ago
Closed 15 years ago
Make notification bar open the Addon Manager in browser rather than its own window
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(blocking-seamonkey2.1 a2+)
RESOLVED
FIXED
seamonkey2.1a2
Tracking | Status | |
---|---|---|
blocking-seamonkey2.1 | --- | a2+ |
People
(Reporter: Callek, Assigned: Callek)
References
Details
Attachments
(1 file, 1 obsolete file)
3.27 KB,
patch
|
neil
:
review+
|
Details | Diff | Splinter Review |
This should enable the notification bar to open a new tab/window depending on prefs instead of loading the Addon Manager like we used to.
Assignee | ||
Comment 1•15 years ago
|
||
Attachment #451210 -
Flags: review?(neil)
Comment 2•15 years ago
|
||
Comment on attachment 451210 [details] [diff] [review]
Just do it
>+ var whereToOpen = self._prefs.getIntPref("browser.link.open_external");
Unfortunately this is an event listener, so "this" refers to the disabled plugin, but there's no "self" either.
Assignee | ||
Comment 3•15 years ago
|
||
This does it, but does not abstract out the common bits; I'm just hoping to get this in for a2 faster, and do the abstraction shortly after in a followup.
Attachment #451210 -
Attachment is obsolete: true
Attachment #452651 -
Flags: review?(neil)
Attachment #451210 -
Flags: review?(neil)
Comment 4•15 years ago
|
||
Comment on attachment 452651 [details] [diff] [review]
v2
For a second I wondered what common bits you were referring to but I worked it out.
Attachment #452651 -
Flags: review?(neil) → review+
![]() |
||
Updated•15 years ago
|
blocking-seamonkey2.1: ? → a2+
Assignee | ||
Comment 5•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Target Milestone: --- → seamonkey2.1a2
![]() |
||
Comment 6•15 years ago
|
||
So, when will browser.chromeURL not be navigator.xul in suite.
+ var browserURL = "chrome://navigator/content/navigator.xul";
+ try {
+ browserURL = self._prefs.getCharPref("browser.chromeURL");
+ } catch (ex) {}
You need to log in
before you can comment on or make changes to this bug.
Description
•