Closed
Bug 121324
Opened 24 years ago
Closed 15 years ago
Tracking bug for ANY changes to prefs (additions, deletions, change in usage)
Categories
(SeaMonkey :: Preferences, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mitchf, Unassigned)
References
()
Details
(Keywords: meta)
Comment 1•24 years ago
|
||
hmm, this seems like a dup [for the most part?] of bug 114521.
*** This bug has been marked as a duplicate of 114521 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 2•24 years ago
|
||
undupping...mitch, is this to track back-end prefs?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Reporter | ||
Comment 3•24 years ago
|
||
Yes, any time an engineer adds, deletes, or changes (behavior or acceptable
values) a preference, it should be noted here. That way TechPubs can update
their prefs documentation, and Customization groups can decide if the pref needs
to be modifiable and lockable by CCK/Factory, and also verify that the pref can
be locked properly.
Comment 4•24 years ago
|
||
This could help prevent corruption of profile data. See bug 123929.
new pref: instroduced by 44070:
[deployment]Match browser's default locale/region to OS's default.
all.js: pref("intl.locale.matchOS", false);
When its value is 'true', browser will inquire the system's locale and set its
UI language and region content to match it. For example, when we install a
Japanese Mach V browser client on an English (US) system, on start up, the client
will use English as its UI language and US as its region locale until a user
profile is selected. If a (pair) of locale is defined in the selected profile,
browser will honor the profile locale. In addition, when cmdline switches,
'-UILocale' and/or 'contentLocale', present, the cmdline switch take precedence.
Note that selecting locale is an expensive operation, therefore, when this
pref is "true", there will be a roughly 30% start up performance drag.
Depends on: 44070
Comment 7•23 years ago
|
||
new pref introduced:
pref("network.cookie.disableCookieForMailNews", true); // disable all cookies
for mail
Bug 22994
This pref is by default true and when true it blocks setting of cookies from
mailnews messages.
other string changes
in mailPrefsOverlay.dtd
+<!ENTITY disableCookieForMailNews.label "Disable cookies in Mail & Newsgroups">
+<!ENTITY disableCookieForMailNews.accesskey "m">
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
The bugscape version of this bug: http://bugscape.netscape.com/show_bug.cgi?id=14392
Comment 9•23 years ago
|
||
pref:
browser.downloadmanager.behavior
determines the behavior upon starting a download.
values:
0 - open the download manager.
1 - open a progress dialog.
2 - do nothing.
Comment 11•23 years ago
|
||
145383:
so, i have some UI changes for the HTTP networking prefs panel that i think are
really important for mozilla1.0.1. bug 145383 is a meta bug with 3 dependencies
(all of the dependencies are simple changes which have been fixed on the trunk
for a while now).
these changes do the following:
1- split up the HTTP networking prefs to allow different settings for direct and
proxy connections. important since we might like to make our default proxy
connections use HTTP/1.0, to maximize compatibility. we currently cannot do
this given that our UI lumps the two settings together. for reference, IE
separates these two as well. bug 60811 adds a little bit of backend machinery
to make this work, and bug 136956 applies the corresponding UI changes.
2- provide useful documentation within the prefs panel to explain what these
options are for. i've also added a warning about pipelining. see bug 145382.
...[snip]
thx!
darin
Depends on: 145383
Comment 12•23 years ago
|
||
107949:
New pref to prevent web authors from creating misleading UI:
+pref("dom.disable_window_open_feature.titlebar", false);
+pref("dom.disable_window_open_feature.close", false);
+pref("dom.disable_window_open_feature.toolbar", false);
+pref("dom.disable_window_open_feature.location", false);
+pref("dom.disable_window_open_feature.directories", false);
+pref("dom.disable_window_open_feature.personalbar", false);
+pref("dom.disable_window_open_feature.menubar", false);
+pref("dom.disable_window_open_feature.scrollbars", false);
+pref("dom.disable_window_open_feature.resizable", false);
+pref("dom.disable_window_open_feature.minimizable", false);
+pref("dom.disable_window_open_feature.status", false);
+
Comment 13•23 years ago
|
||
See http://bugzilla.mozilla.org/show_bug.cgi?id=107949#c50 for usage.
Comment 14•21 years ago
|
||
From bug 86193:
dom.event.contextmenu.enabled
Defaults to "true".
Set to "false" to prevent websites from blocking use of the context menu.
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•18 years ago
|
Assignee: bugs → prefs
QA Contact: bugzilla
Comment 15•18 years ago
|
||
Now that all dependencies of this bug have been closed, can this tracking bug now be closed?
Comment 16•17 years ago
|
||
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
![]() |
||
Comment 17•15 years ago
|
||
> Now that all dependencies of this bug have been closed, can this tracking bug
> now be closed?
Agreed.
Status: NEW → RESOLVED
Closed: 24 years ago → 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•