Open
Bug 496429
Opened 15 years ago
Updated 2 years ago
Clean up /mailnews/mailnews.js
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: mnyromyr, Unassigned)
References
Details
With bug 390262 fixed, many of the default prefs defined in /mailnews/mailnews.js are used solely outside of mailnews, eg. in UI code specific to SM or TB. Some of these are even already overwritten in SM's browser-prefs.js (sic!) or in TB's all-thunderbird.js...
I'd propose keeping only those prefs in /mailnews/mailnews.js which are actually used by code under /mailnews and moving everything else into /suite/mailnews/mailnews.js and /mail/app/profile/all-thunderbird.js, respectively.
Comments?
Comment 1•15 years ago
|
||
What will you do with prefs that are different in SM versus TB, but are used by mailnews/ code?
Otherwise I think its a great idea.
Reporter | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> What will you do with prefs that are different in SM versus TB, but are used by
> mailnews/ code?
There's no "best" solution in this case, so I'd just keep their current definitions and overwritten values where they are (modulo moving any overwrites out of browser-prefs.js in /suite).
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Severity: S3 → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•