Closed Bug 121324 Opened 23 years ago Closed 14 years ago

Tracking bug for ANY changes to prefs (additions, deletions, change in usage)

Categories

(SeaMonkey :: Preferences, enhancement)

All
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mitchf, Unassigned)

References

()

Details

(Keywords: meta)

 
Keywords: meta
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: 23 years ago
Resolution: --- → DUPLICATE
undupping...mitch, is this to track back-end prefs?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
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.
This could help prevent corruption of profile data. See bug 123929.
bug 134001 contains changes to pref.
Depends on: 134001
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
Depends on: 22994
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 &amp; Newsgroups">
+<!ENTITY disableCookieForMailNews.accesskey "m">



Status: UNCONFIRMED → NEW
Ever confirmed: true
Depends on: 137440
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.
-> Default owner
Assignee: sgehani → ben
Depends on: 133282
No longer depends on: 133282
Depends on: 141247
No longer depends on: 141247
Depends on: 133282, 141247
Depends on: 137886
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
Depends on: 107949
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);
+
Depends on: 80035
Depends on: 175199
No longer depends on: 175199
Depends on: 166648
From bug 86193:

dom.event.contextmenu.enabled

Defaults to "true".
Set to "false" to prevent websites from blocking use of the context menu.
Product: Browser → Seamonkey
Assignee: bugs → prefs
QA Contact: bugzilla
Now that all dependencies of this bug have been closed, can this tracking bug now be closed?
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
> Now that all dependencies of this bug have been closed, can this tracking bug
> now be closed?

Agreed.
Status: NEW → RESOLVED
Closed: 23 years ago14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.