4
*** Please submit non packaging issue (e.g. feature requests) bugs to
5
the Debian BTS and the upstream bugzilla
6
(http://bugzilla.mozilla.org/buglist.cgi?product=Firefox) and put a
7
reference to the bugzilla bug in the Debian bug report, to ease bug
8
triage for the maintainer. Thank you. ***
10
Firefox is still in heavy development, and it does not fully support
11
upgrading from one release to another. Moving your .mozilla/firefox
12
directory out of the way should be your first course of action before
13
filing a bug report. Please see #202130 for an excellent analysis. You
14
may also want to try removing ~/.mozilla/firefox/default/*/XUL.mfasl.
16
Firefox requires the loopback interface (lo) to be up and unfiltered
17
to accept keyboard input and function correctly. Please make sure this
18
is the case before filing any bugs.
23
From version 1.5beta1 onwards, the automatic application update has been
24
disabled through the app.update.enabled preference, which is locked to
25
'false' by /usr/lib/mozilla-firefox/greprefs/firefox.cfg.
27
Automatic extensions update, which used to be disabled; has been re-enabled,
28
since the Extensions Manager has a correct behaviour with system-wide
29
installed extensions now.
34
From Firefox 0.9, "old" extensions are disabled at first run (i.e.
35
when no profile was found). By old extensions, Firefox means extensions
36
not following the new extensions guidelines described at:
37
http://www.bengoodger.com/software/mb/extensions/packaging/extensions.html
38
But even the ones following these guidelines can be considered old if the
39
contents.rdf file in their chrome gives the attribute chrome:extension =
40
"true" in the package information.
42
Some extensions can also get disabled by a new release of Firefox, because
43
the install.rdf file provided by the extension says it's targetted for a
44
maximum version older than the current one.
49
With older versions of Firefox, an update-mozilla-firefox-chrome script was
50
provided so that extensions are correctly enabled in Firefox. This has been
51
obsoleted by the new Extensions Manager, and the update-mozilla-firefox-chrome
52
script removed. Packages that use this script to support older versions of
53
Firefox are advised to check for its presence before using it.
58
By default, firefox detects and runs the correct dsp wrapper for esd
59
or arts. If this is not the desired behaviour, edit
60
/etc/mozilla-firefox/mozilla-firefoxrc or ~/.mozilla-firefoxrc and set
61
the FIREFOX_DSP variable to:
63
"auto": The default, auto-detection.
69
"none": Don't use any sound wrapper.
72
using Java. (You should use plugin which compiled with gcc-3.2)
75
Grab a binary Java distribution from http://java.sun.com/. Install the
76
java-package package and do a make-jpkg on the file.
81
Some people have complained that the button order in dialogs is
82
non-intuitive (ie, they don't like it). To reverse the order, add the
83
following to your chrome/userChrome.css file, under the
84
~/.mozilla/firefox directory:
86
.dialog-button-box { -moz-box-direction: reverse; -moz-box-pack: right; }
87
.dialog-button-box spacer { display: none ! important; }
92
Versions of Firefox before 1.0 supported Emacs style keybindings in
93
text entry boxes. Version 1.0 now merely follows the GTK keybindings
94
settings. To enable Emacs keybindings in GTK, follow the instructions
95
at http://kb.mozillazine.org/Emacs_Keybindings_(Firefox).
97
-- Mike Hommey <glandium@debian.org>, Fri Sep 9 17:30:50 CEST 2005