user.js



# user.js - Configuration file for Mozilla-technology browsers.
# Revision: 111005

#---------------------------------------------------------------------

# This is an  optimized "user.js"  configuration file for web browsers
# based on  Mozilla technology,  including Mozilla Firefox (tm),  Sea-
# monkey (tm), and similar programs.

# Important: If you modify this file, you must follow three rules:
#
#     (a) Avoid typos. If you make a mistake on one line, your browser
#         may ignore  subsequent lines without warning you.  For exam-
#         ple,  don't forget to put  double quotes  around  a variable
#         name (e.g., "extensions.update.enabled").
#
#     (b) Use a text editor (not AbiWord, OpenOffice, MS-Word, etc.).
#
#     (c) The text editor must  support long lines,  and it must *not*
#         wrap them.

# Disclaimer: If you decide to  use  this file or  any of the settings
# provided here, you assume all responsibility for any issues that may
# arise.

# The original author believes  that  these  settings  are "optimized"
# for  his  purposes, and has used  various versions  of this file for
# approx. five years. However, these settings  may not  be appropriate
# for  all users  and all circumstances.  The following information is
# provided  without  assurances,  guarantees,  or  warranties  of  any
# kind.

#---------------------------------------------------------------------

# This setting makes pages load faster. Note: This works best for fast
# systems with fast connections.

# IMHO:  "nglayout.initialpaint.delay" should be normally be  equal to
# 100.  The appropriate range is 100  to 1000.  Note that the  related
# "content" settings may need to be  adjusted  when  this parameter is
# changed.

user_pref("nglayout.initialpaint.delay", 100);

#---------------------------------------------------------------------

# These "content" settings should  produce a browser that  feels fast-
# er.

# Smaller values of  "content.notify.interval" improve responsiveness.
# However,  contrary to  recommendations  on the Internet,  it appears
# that this parameter shouldn't be set to a value below 100000.

# Note: If "nglayout.initialpaint.delay" is non-zero, "content.notify.
# interval" should apparently be  equal to 1000 times  "nglayout.init-
# ialpaint.delay".

# "content.switch.threshold" should be equal to "content.notify.inter-
# val".

# "content.max.tokenizing.time" should be a multiple of "content.noti-
# fy.interval". Recommended setting: Use triple the latter value.

user_pref("content.interrupt.parsing", true);
user_pref("content.max.tokenizing.time", 300000);
user_pref("content.notify.backoffcount", 10);
user_pref("content.notify.interval", 100000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 100000);

#---------------------------------------------------------------------

# These settings enable and configure "HTTP pipelining".  On most sys-
# tems, this should speed things up a little.

# Note: The "firstrequest" setting shown here apparently isn't used by
# current browsers.

user_pref("network.http.pipelining", true);
user_pref("network.http.pipelining.firstrequest", true);
user_pref("network.http.pipelining.maxrequests", 8);
user_pref("network.http.proxy.pipelining", true);

#---------------------------------------------------------------------

# Adjust HTTP connection limits.  Note:  Don't increase these settings
# significantly. If you raise the numbers too far, problems may occur.
# For example, site administrators may blacklist you.

user_pref("network.http.max-connections", 64);
user_pref("network.http.max-connections-per-server", 16);
user_pref("network.http.max-persistent-connections-per-proxy", 16);
user_pref("network.http.max-persistent-connections-per-server", 8);

#---------------------------------------------------------------------

# Adjust DNS limits:

# For these two parameters, larger settings decrease the number of DNS
# lookups  made over time.  This speeds things up, but it's a bad idea
# to use excessive values.

# The  cache-expiration parameter should  probably be  capped at 86400
# (the units are seconds,  and 86400 seconds is  equal to one day).  I
# don't know what the optimum setting is for the  cache-entries param-
# eter.  However, if you've got adequate RAM, 1024 is probably a reas-
# onable value.

user_pref ("network.dnsCacheExpiration", 86400);
user_pref ("network.dnsCacheEntries", 1024);

#---------------------------------------------------------------------

# Display web-site "favicons":

# "favicons" are  small pictures associated with individual web sites.
# The following three settings enable "favicons",  both in the address
# bar and  next to web sites  in the bookmark list.  ("favicons" won't
# be displayed until you either  visit or bookmark  web sites that use
# them.)

# Note:  These settings may  cause web pages that  you've saved and/or
# bookmarks that you've created to access the original web sites with-
# out your permission.  IMHO:  This isn't a major security issue,  be-
# cause access is limited to intermittent retransfers  of the original
# "favicons".

# If you're concerned about the "favicons" site-access issue, comment-
# out  the "load_toolbar_icons" line  below  and change the  other two
# settings from true to false.

user_pref("browser.chrome.favicons", true);
user_pref("browser.chrome.load_toolbar_icons", 2);
user_pref("browser.chrome.site_icons", true);

#---------------------------------------------------------------------

# These  three settings force  most new pages  to load in  the current
# window.

user_pref("browser.block.target_new_window", true);
user_pref("browser.link.open_newwindow", 1);
user_pref("browser.link.open_newwindow.ui", 1);

#---------------------------------------------------------------------

# These four settings make some general changes:
#
#     (a) Disable blinking text
#     (b) Show tabs whether or not there's more than one window open
#     (c) Disable warning about closing more than one tab
#     (d) Enable smooth scrolling

user_pref("browser.blink_allowed", false);
user_pref("browser.tabs.autoHide", false);
user_pref("browser.tabs.warnOnClose", false);
user_pref("general.smoothScroll", true);

#---------------------------------------------------------------------

# These settings enable keyword browsing through one of several possi-
# ble  search engines.  This is a time-saving feature that reduces the
# need for separate  search toolbars.  To use this feature, just enter
# two or more words in the  browser's location field.  You can double-
# quote phrases, if necessary,  but don't use any embedded punctuation
# (commas, periods, etc.).

user_pref("browser.fixup.alternate.enabled", false);
user_pref("keyword.enabled", true);

# To select the desired search engine,  uncomment exactly _one_ of the
# following "keyword.URL" settings.

# Warning:  The "keyworld.URL" line used for  Google is about 177 col-
# umns wide.  If you modify this file,  use a text editor that doesn't
# wrap long lines (or clip them).

# Search engine #1:  For Clusty,  uncomment this "keyword.URL" setting
# and comment-out the others.
#
# user_pref("keyword.URL", "http://clusty.com/search?query=");

# Search engine #2:  For Google,  uncomment this "keyword.URL" setting
# and comment-out the others.
#
user_pref("keyword.URL", "http://www.google.com/search?num=100&hl=en&ie=UTF-8&oe=UTF-8&btnG=Google+Search&lr=lang_en&as_ft=i&&as_qdr=all&as_occt=any&as_dt=i&safe=images&as_q=");

# Search engine #3:  For  Yahoo,  uncomment this "keyword.URL" setting
# and comment-out the others.
#
# user_pref("keyword.URL", "http://search.yahoo.com/search?fr=FP-pull-web-t&n=40&p=");

#---------------------------------------------------------------------

# By default,  Mozilla-technology browsers  display dialog boxes  when
# you move from ordinary pages to secure pages  and vice  versa.  Some
# browsers display the dialog boxes every time that the transition oc-
# curs.  Other browsers only display the dialog boxes once.  These two
# settings disable the dialog boxes completely, regardless.

user_pref("security.warn_entering_secure", false);
user_pref("security.warn_leaving_secure", false);

#---------------------------------------------------------------------

# These  five settings should eliminate most popup windows,  including
# some popups that use advanced techniques.

# Note:  These changes won't suppress  popups completely,  but they'll
# make a big difference.

user_pref("dom.disable_open_during_load", true);
user_pref("dom.popup_allowed_events", "change dblclick reset submit");
user_pref("privacy.popups.first_popup", false);
user_pref("privacy.popups.remove_blacklist", false);
user_pref("privacy.popups.statusbar_icon_enabled", false);

#---------------------------------------------------------------------

# Additional Javascript security measures:

# The  settings in  the preceding section eliminate  some  Javascript-
# based popups. The three settings below impose  more  limits on Java-
# script. These settings should make it  more difficult  for web sites
# to hijack the browser.

user_pref("dom.event.contextmenu.enabled", false);
user_pref("dom.disable_window_open_feature.status", true);
user_pref("dom.disable_window_status_change", true);

#---------------------------------------------------------------------

# Disable one Javascript security measure:

# This setting disables one Javascript security measure. If you'd like
# to use Javascript bookmarklets to move or resize the browser window,
# this step is necessary. If you don't care about move/resize support,
# you can set this parameter to true.

user_pref("dom.disable_window_move_resize", false);

#---------------------------------------------------------------------

# This is another security measure:

# It appears that  a web standard  named  "SOAP"  may allow  web pages
# and/or E-mail to  contact servers and  transmit  information without
# your permission.

# To quote one writer discussing SOAP: "SOAP is extremely unsafe since
# it has  access to [DNS] and  the  underlying windows system.  It can
# totally bypass any firewall since messaging is web page to web page.
# COM  controls  can be  written to  phone home  via  SOAP  just as in
# HTTP".

# I don't know  if all of this is true,  but  I've added the following
# three settings to disable SOAP. Note: These settings may break SOAP-
# based applications.

user_pref("capability.policy.default.SOAPCall.invokeAsync", "NoAccess");
user_pref("capability.policy.mailnews.SOAPCall", "NoAccess");
user_pref("capability.policy.default.SOAPCall.invoke", "NoAccess");

#---------------------------------------------------------------------

# Miscellaneous security measures:

# The "browser.related.enabled" setting used here disables the "What's
# Related" feature. This prevents various  potential security problems
# (loss of privacy, possible  attacks  through  DNS  cache  poisoning,
# etc.).

# The "capability.policy" setting is a work-around for an old  Mozilla
# bug.  It prevents websites from  being able to see the URLs of pages
# visited  after them.  AFAIK,  this setting  isn't  needed  for newer
# browsers.

# The "network.protocol-handler" setting is a  work-around for an  MS-
# Windows  security problem.  It  disables  the use of  the MS-Windows
# "shell:" protocol.

user_pref("browser.related.enabled", false);
user_pref("capability.policy.default.Window.onunload", "noAccess");
user_pref("network.protocol-handler.external.shell", false);

#---------------------------------------------------------------------

# The "redirection-limit" setting limits the  number of HTTP redirects
# that the  browser will accept.  If you  encounter a  large number of
# HTTP redirects,  something is  probably wrong.  However,  this limit
# shouldn't be set too low, or it'll break legitimate web sites. 10 is
# probably a reasonable value.

# Note:  MozillaZine states that this preference only affects HTTP re-
# directs. It doesn't stop redirects caused by HTML meta tags or Java-
# script code.

user_pref("network.http.redirection-limit", 10);

#---------------------------------------------------------------------

# Mozilla-technology  browsers  support a  feature  called  "link pre-
# fetch".  "Link prefetch" can  cause a number of problems,  including
# slow performance, superfluous cookies, etc.  It's especially proble-
# matic on systems with unreliable DNS. The following setting disables
# "link prefetch".

user_pref("network.prefetch-next", false);

#---------------------------------------------------------------------

# Some  Mozilla-technology  browsers  have a  security hole  known  as
# "pings".  This  security  hole allows  third parties to  track users
# silently. Affected browsers don't provide any notification that this
# is happening.  To correct the problem, this code sets "browser.send_
# pings" equal to false.

# Note: Internet Explorer advocates could legitimately cite "pings" as
# an example of  spyware in  Mozilla-technology browsers.  However, it
# should be noted that Internet Explorer's record with respect to spy-
# ware, security holes, etc., can't be described as pristine. In 2004,
# the  U.S. Government's  Computer Emergency Readiness Team  (US-CERT)
# issued a warning to the effect that  Internet Explorer was  too dan-
# gerous for everyday use.

user_pref("browser.send_pings", false);

#---------------------------------------------------------------------

# The following three settings  close another potential security hole.
# Specifically, they disables a feature that allowed companies such as
# Google (and DoubleClick, through Google) to  build a complete record
# of all web sites visited.

user_pref("browser.safebrowsing.enabled", false);
user_pref("browser.safebrowsing.malware.enabled", false);
user_pref("browser.safebrowsing.remoteLookups", false);

#---------------------------------------------------------------------

# Mozilla-technology  browsers  have a feature that  breaks  some  web
# pages and extensions.  Specifically, if Javascript code doesn't exe-
# cute  quickly enough,  the browsers assume that  something is wrong,
# and they display dialog boxes.

# When this happens, the user must click a button to continue.  If the
# user clicks  the wrong button,  the current  Javascript operation is
# aborted.  As an added bonus, in some cases,  the  dialog boxes  will
# appear repeatedly.

# Note: This issue is  especially problematic for the Scrapbook exten-
# sion, which needs a significant amount of  time to process large web
# pages.

# To address  the problem,  this code  increases  two related  timeout
# values to reasonable levels.  This won't fix the problem 100% of the
# time,  but it would be a bad idea to disable the timeouts  complete-
# ly.

user_pref("dom.max_chrome_script_run_time", 50);
user_pref("dom.max_script_run_time", 50);

#---------------------------------------------------------------------

# This setting  bypasses a problem that  occurs with  some older brow-
# sers.

user_pref("content.maxtextrun", 8191);

#---------------------------------------------------------------------

# "config.trim_on_minimize" affects  browser performance under MS-Win-
# dows. As of late 2007,  this parameter doesn't affect anything under
# UNIX. If the setting is true, MS-Windows browsers  will release some
# memory when they're iconized. If it's false, MS-Windows browsers may
# use more memory on average, but they'll deiconize faster. Presently,
# the suggested setting is false.

user_pref("config.trim_on_minimize", false);

#---------------------------------------------------------------------

# This parameter sets a minimum size of 11 points for Western fonts.

user_pref("font.minimum-size.x-western", 11);

#---------------------------------------------------------------------

# Newer  Mozilla-technology browsers have  a feature that  some people
# will find irritating.

# The  Mozilla developers wanted to reduce  potential problems related
# to trojans, so they made it more difficult to install browser exten-
# sions.

# If you'd like to use the  original mode  of operation  (unrestricted
# installation),  set the following  "xpinstall..." parameter equal to
# false.

# If you'd like to use the slower (and more irritating) mode of opera-
# tion, set the parameter equal to true.

# Note:  AFAIK, this setting doesn't affect the most important instal-
# lation security measure (the  installation prompt).  Whether  or not
# you use  this setting,  standard browsers should ask you  to confirm
# all installation attempts.

user_pref("xpinstall.whitelist.required", false);

#---------------------------------------------------------------------

# IMHO:  It's a bad idea to update browser extensions and themes auto-
# matically.  In some cases, these items have forked, and auto-updates
# may  install  the wrong versions.  In other cases,  new versions may
# break your current setup because of  bugs or backwards-compatibility
# issues.

# I prefer to update items of this type manually. Therefore, I use the
# following two settings.  These settings disable auto-updates for the
# items in question.

# Note:  These settings don't affect auto-updates of the core browser.
# Additionally, they don't prevent updates of extensions (etc.). These
# settings  just disable the browser's pro-active behavior in this re-
# gard.

user_pref("extensions.update.enabled", false);
user_pref("extensions.update.autoUpdateEnabled", false);

#---------------------------------------------------------------------

# This section disables additional  auto-update operations.  If you're
# using a  specially-constructed  browser  package,  don't modify this
# section. If you're using a generic (unmodified) web browser, you can
# comment-out these settings.

# Setting                         Disables
# -----------------------------   ------------------------------------
# app.update.auto       = false   Auto-downloads of "MAR" files
# app.update.enabled    = false   Core-program    update checks
# browser.search.update = false   "Search"-plugin update checks

user_pref("app.update.auto", false);
user_pref("app.update.enabled", false);
user_pref("browser.search.update", false);

#---------------------------------------------------------------------

# This sets the maximum number of pages  stored  per tab  in the brow-
# ser's session history.

user_pref("browser.sessionhistory.max_entries", 25);

#---------------------------------------------------------------------

# Circa 2005, Mozilla-technology browsers added a nice feature: faster
# Back/Forward  operations.  This feature is  controlled by one of the
# following two parameters:
#
#     browser.sessionhistory.max_total_viewers        (newer browsers)
#     browser.sessionhistory.max_viewers              (older browsers)
#
# To be on the safe side,  this  configuration file  sets both parame-
# ters.

# Bigger numbers  produce  faster results,  but they also consume more
# memory (probably about 4MB per unit). Presently, we're using a value
# of five.  If you're low on system memory,  set both parameters equal
# to zero.

user_pref("browser.sessionhistory.max_total_viewers", 4);
user_pref("browser.sessionhistory.max_viewers", 4);

#---------------------------------------------------------------------

# After  you download  something, the Download Manager displays a list
# of previously-downloaded files. That's not a problem, by itself, but
# the default behavior is for the list to grow forever, even after you
# exit the browser. You can clear the  list manually,  but I prefer to
# have the browser  do it  at the end  of each session.  The following
# setting selects this mode.

user_pref("browser.download.manager.retention", 1);

#---------------------------------------------------------------------

# Some Mozilla-technology browsers provide a feature that automatical-
# ly resizes  large images when  they're  viewed directly.  Note: This
# feature doesn't apply to images that are viewed in a normal web-page
# context.

# This  feature supports  two modes:  Display images  full-size or re-
# duced.  You can toggle  back and forth between the two modes at run-
# time.

# The "reduced" mode produces good results for true-color images (such
# as photographs).  However, the results are very poor for things like
# line drawings and stock charts.

# This wouldn't be  a problem if the default mode was full-size.  How-
# ever, the default mode is "reduced".  IMHO: Images shouldn't be dis-
# played incorrectly  by default.  This is irritating, and may confuse
# new users. Therefore,  I use  the following setting. It disables the
# auto-resize feature.

user_pref("browser.enable_automatic_image_resizing", false);

#---------------------------------------------------------------------

# External programs or scripts can ask  Mozilla-technology browsers to
# open new links.  This feature is used (for example)  for things like
# "help" screens.  The  following setting specifies  where to put  web
# pages requested by external software.

# Three modes are supported:
#
# Value   Placement of external pages
# -----   ----------------------------------
#   1     in the current tab/window
#   2     in a new window
#   3     in a new tab in the current window

# I prefer mode one, for a simple reason: If you select anything else,
# pressing "Help" (etc.) in  external programs  may open an  unlimited
# series of tabs (or windows).

# If you don't want to see an unlimited series of  tabs  (or windows),
# set this parameter equal to 1. This is the recommended mode.

# If  you'd  like  to  see an unlimited series of  tabs  (or windows),
# set this parameter equal to 2 or 3.

user_pref("browser.link.open_external", 1);

#---------------------------------------------------------------------

# Mozilla-technology browsers support  an option that blocks the load-
# ing of third-party images. This mode eliminates some web-bugs and/or
# advertising  images. However, it also breaks numerous legitimate web
# sites. Additionally, it's too easy to enable this option accidental-
# ly.

# The following setting disables the option.  Note: Mozilla-technology
# browsers can also  block  images from specific web sites.  This is a
# separate feature.  This  change  doesn't affect  specific-site image
# blocking.

# IMHO:  Neither of the image-blocking features is  especially good at
# blocking  web-bugs and/or  advertising images.  I recommend that you
# use two browser extensions named  Adblock Plus and NoScript instead.
# You'll need to make some adjustments (based on your needs),  but the
# effort will be  worth it.  Note: Use Adblock Plus, not  Adblock. The
# two extensions  are similar.  However, as of mid-2006,  Adblock Plus
# is more powerful.

# If you install Adblock Plus and/or NoScript,  you should change some
# of the default  parameters  used. The recommended settings are docu-
# mented in the following sections.

user_pref("permissions.default.image", 1);

#---------------------------------------------------------------------

# Adblock Plus is an excellent ad-blocking extension.  If Adblock Plus
# is installed, these settings adjust the  behavior of  the extension.
# Specifically, they remove a large Adblock Plus icon from the naviga-
# tion  toolbar and  replace  it  with a  smaller icon in  the  status
# bar.

user_pref("extensions.adblockplus.showintoolbar", false);
user_pref("extensions.adblockplus.showinstatusbar", true);

#---------------------------------------------------------------------

# Download Manager Tweak  is an  extension that modifies the browser's
# Download Manager. This  setting  affects the  Download Manager Tweak
# extension (not the Download Manager itself).

# The standard Download Manager opens a separate window, and  this can
# be  irritating.  By default,  Download  Manager  Tweak emulates  the
# standard behavior. This setting tells the extension to use a tab in-
# stead of a separate window.

# If you prefer the  standard behavior (separate window),  comment-out
# this setting. If you'd like to display download results in the brow-
# ser sidebar, change 2 to 1 here.

user_pref("extensions.downloadmgr.windowType", 2);

#---------------------------------------------------------------------

# ForecastFox is an extension  that reports  current and upcoming wea-
# ther conditions.

# If ForecastFox is installed, this section makes the following chang-
# es:
#
#       (a) It  disables  an  irritating  "Current Conditions"  popup.
#           Note:  ForecastFox  provides a  separate  "Severe Weather"
#           popup. That feature isn't affected.
#
#       (b) It tells  ForecastFox to display just  icons on the status
#           bar.  Note:  This change is recommended.  If it's omitted,
#           ForecastFox may take up most of the status bar. FWIW: This
#           change doesn't affect  tooltips.  To get detailed informa-
#           tion about a  given day,  just  move  the cursor  over the
#           associated icon.

user_pref("forecastfox.cc.panel.display", 0);
user_pref("forecastfox.cc.slider.enabled", false);
user_pref("forecastfox.dayf.panel.display", 0);
user_pref("forecastfox.dayt.panel.display", 0);

#---------------------------------------------------------------------

# NoScript is a  security-related  extension that  disables Javascript
# for "untrusted" web sites.

# This code makes two changes that affect NoScript:

# 1. By default,  NoScript displays messages  about  blocked code  for
# most  major web sites  (excluding sites that are flagged as  "trust-
# ed").  The messages are distracting,  since they pop up  quite  fre-
# quently.  Additionally,  they're superfluous.  The messages  provide
# diagnostic information,  but ordinary users won't be able to  under-
# stand it,  and there's a separate NoScript  status indicator  that's
# sufficient  for  most purposes.  The  "noscript.notify" setting used
# here (false) disables the messages.

# 2. Some  Mozilla-technology browsers  have a  security hole known as
# "pings",  as explained previously.  NoScript uses  two  related set-
# tings:  "browser.send_pings"  (which enables one class of pings) and
# "noscript.noping"  (which  disables  another  class). "browser.send_
# pings" was set equal to false  at an  earlier  point.  "noscript.no-
# ping" is set equal to true here.  These settings are recommended for
# security-conscious users.

user_pref("noscript.notify", false);
user_pref("noscript.noping", true);

#---------------------------------------------------------------------

# SwitchProxy is an extension  that  makes it  easier to  manage proxy
# servers.

# If SwitchProxy is installed, this code enables the extension's stat-
# us-bar field and disables  the  associated  toolbar.  If you  prefer
# things the other way around, reverse  the  true and  false  settings
# specified below.

# Note:  It's a good idea to force the appropriate user interface mode
# here.  If this section  is omitted,  badly-constructed  websites may
# cause the  default interface to disappear.  This seems to be a Java-
# script problem related to browser windows.

user_pref("switchproxy.display.statusbar", true);
user_pref("switchproxy.display.toolbar", false);

#---------------------------------------------------------------------

# Tab Mix Plus is an  extension that adds  numerous useful "tab" feat-
# ures. If Tab Mix Plus is installed, these settings adjust the behav-
# ior of the extension,  excluding  its  session manager.  The session
# manager is addressed separately in the next section.

# Details:
#
#   duplicateMenu    = true  - Enables duplicate-tab command
#   hideTabBarButton = false - Don't hide close-tab button on right
#   minWidth         = 100   - Sets minimum tab width to 100 pixels
#   tabBarMaxRow     = 4     - Sets maximum number of tab rows to 4
#   tabBarMode       = 2     - Displays multiple tab rows if necessary
#   tabBarSpace      = true  - Makes add/remove buttons less crowded
#   tabmix.tabXMode  = 0     - Don't put a close button on each tab
#   useUnreadColor   = false - Don't colorize unread tabs

# Note:  Firefox 2.0 and  Tab Mix Plus have  different conventions re-
# lated to tab overflow.  The browser uses scrolling to handle a large
# number  of  tabs,  and  Tab Mix Plus (optionally) uses  multiple tab
# rows.  If Tab Mix Plus is installed,  its approach  apparently takes
# precedence.

user_pref("extensions.tabmix.duplicateMenu", true);
user_pref("extensions.tabmix.hideTabBarButton", false);
user_pref("extensions.tabmix.minWidth", 100);
user_pref("extensions.tabmix.tabBarMaxRow", 4);
user_pref("extensions.tabmix.tabBarMode", 2);
user_pref("extensions.tabmix.tabBarSpace", true);
user_pref("extensions.tabmix.tabXMode", 0);
user_pref("extensions.tabmix.useUnreadColor", false);

#---------------------------------------------------------------------

# Tab Mix Plus includes a sessions manager;  i.e., a facility that can
# preserve tabs across sessions.  Firefox 1.5  didn't  have this feat-
# ure,  but Firefox 2.0 does. Therefore (IMHO), Tab Mix Plus's session
# manager should be disabled. To accomplish this, we set the following
# three parameters equal to false.

user_pref("extensions.tabmix.sessions.crashRecovery", false);
user_pref("extensions.tabmix.sessions.manager", false);
user_pref("extensions.tabmix.sessionToolsMenu", false);

#---------------------------------------------------------------------

# By default, Firefox includes a "Go" button to the right of the loca-
# tion  field. This button is  rarely used,  and it consumes  valuable
# real estate. Fortunately,  it's optional.  The following setting re-
# moves the button.

user_pref("browser.urlbar.hideGoButton", true);

#---------------------------------------------------------------------

# The parameter "browser.cache.memory.capacity"  can be  used to limit
# the amount of RAM used by the browser to cache certain kinds of obj-
# ects.  If the setting is -1,  the browser  decides the limit for it-
# self.  If the setting is a positive integer,  it specifies the maxi-
# mum amount of RAM to use,  expressed  in kilobytes.  Typical  values
# might be 8192 or 10240.

user_pref("browser.cache.memory.capacity", 16384);

#---------------------------------------------------------------------

# Firefox  2.0 adds a  tab-close button to  _every_ tab. This is  ill-
# advised. The redundant  buttons  consume  real estate. Additionally,
# they lead to accidental tab-closes.  The  following setting replaces
# the  per-tab "close" buttons with a single tab-close button (located
# on the right side of the "tab" bar).

# Note:  If Tab Mix Plus is installed, its  settings  take  precedence
# over this one. For the setting below to  work, you  may need  to set
# "extensions.tabmix.hideTabBarButton" to false. This file already in-
# cludes the setting in question.

user_pref("browser.tabs.closeButtons", 3);

#---------------------------------------------------------------------

# As you open  new tabs, Firefox 2.0 reduces the width of the existing
# tabs down to a certain size,  then  switches to a  horizontal-scroll
# mode. The  following  parameter sets the minimum tab width  (in pix-
# els). Try values from 75 to 100.

user_pref ("browser.tabs.tabMinWidth", 85);

#---------------------------------------------------------------------

# By default, some Mozilla-technology browsers treat the backspace key
# as a navigation key. This can cause data loss. To prevent data loss,
# the following setting suppresses the feature in question.

# Note: This setting works for Firefox 2.0 through Firefox 3,  but not
# for very old browsers.

user_pref("browser.backspace_action", 2);

#---------------------------------------------------------------------

# If the PrefBar extension is installed, this setting disables associ-
# ated update notifications;  i.e., messages that tell the user to up-
# date.  This setting  is recommended. IMHO: Automated updates  and/or
# update notifications are a bad idea. The simple fact is that updates
# frequently break things.

user_pref("extensions.prefbar.updatenotify.enabled", false);

#---------------------------------------------------------------------

# This setting  addresses an  issue reported by  "mozilla.com",  which
# posted the following advice:  "Some financial institutions use  port
# 563 for  secure logins,  which results  in an error message.  If you
# encounter this error,  make sure that network.security.ports.banned.
# override includes 563 in the  comma-separated list of banned network
# ports to override".

user_pref("network.security.ports.banned.override", "563");

#---------------------------------------------------------------------

# By  default, some Mozilla-technology browsers insert a delay of sev-
# eral seconds when users try to install extensions. The delay is  ir-
# ritating and serves no real purpose. The following setting  disables
# the delay.

# Note: This setting works for Firefox 1.5 through Firefox 3,  but not
# for very old browsers.

user_pref("security.dialog_enable_delay", 0);

#---------------------------------------------------------------------

# By default, if you use the "about:config" feature,  Mozilla-technol-
# ogy browsers may display an irritating warning message.  The follow-
# ing setting disables the message,

user_pref("general.warnOnAboutConfig", false);

#---------------------------------------------------------------------

# We've been unable to locate  official documentation  related  to the
# following setting. However, if this setting does, in fact, exist, it
# should be set to false.  If it's set to true,  it may  block the in-
# stallation of legitimate add-ons.

user_pref("xpinstall.whitelist.required", false);

#---------------------------------------------------------------------

# Firefox 3  added a new  "autocomplete" feature to the location  bar.
# The "autocomplete" feature produces a list that's too long,  in some
# cases. The following setting reduces the maximum list size to a rea-
# sonable level.

user_pref("browser.urlbar.maxRichResults", 6);

#---------------------------------------------------------------------

# The following two settings are an  attempt to fix a serious security
# problem.  Firefox 3 ignores "Clear Private Data" operations for por-
# tions of its "places" database.  Supposedly, these two settings will
# fix the problem.  However,  as of late 2008, this  hasn't been veri-
# fied.

user_pref("places.frecency.typedVisitBonus", 0);
user_pref("places.frecency.unvisitedTypedBonus", 0);

#---------------------------------------------------------------------

# The  following setting affects Firefox 3.5.X and up.  It slows Java-
# script processing down,  but  prevents some otherwise  uncorrectable
# crashes.

user_pref("javascript.options.jit.content", false);

#---------------------------------------------------------------------

# The  following setting affects  Firefox 3.5.X and up.  It  tells the
# browser that closing the last open tab shouldn't close the main win-
# dow.

user_pref("browser.tabs.closeWindowWithLastTab", false);

#---------------------------------------------------------------------

# The following setting speeds up menu operations.

user_pref("ui.submenuDelay", 0);

#---------------------------------------------------------------------

# The  following setting specifies  RSS update frequency.  The numeric
# parameter is the desired time interval, in seconds.

user_pref("browser.bookmarks.livemark_refresh_seconds", 1800);

#---------------------------------------------------------------------

# The following setting allows  users to  paste text  using the middle
# mouse button.

user_pref("middlemouse.paste", true);

#---------------------------------------------------------------------

# The following setting affects Firefox 3.6.0 and up.  It restores the
# old conventions used for tab placement.

user_pref("tabs.insertRelatedAfterCurrent", false);

#---------------------------------------------------------------------

# The following setting bypasses a bug in IceCat 3.6.0.

user_pref("browser.allTabs.previews", false);

#---------------------------------------------------------------------

# These two settings fix  a color problem  that occurs with  PNG files
# and may also speed things up slightly.  Note: The  color problem in-
# volves blue shifting towards purple.

user_pref("gfx.color_management.enabled", false);
user_pref("gfx.color_management.mode", 0);



To continue, press the browser's Back button.