You are currently viewing a snapshot of taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to, please file a bug.

Mozilla 1.4 Beta Release Notes

To avoid incompatibility problem with previous versions, the Mozilla installer will prompt you to delete the install directory if it is not empty. Answer NO if you put your profile or other personal files in the install directory, otherwise the files will be deleted. Users who put profiles in the default location are not affected.

See the profile FAQ for help on backing up your profiles.

These release notes describe system requirements, installation instructions, and known issues for Mozilla 1.4 Beta. These release notes are updated when we receive feedback, so please check back for new information. Consult our releases page to download the source and thelatest version of Mozilla for your platform. See our end user documentation section for more information on using and configuring Mozilla.

Use Bugzilla to report bugs. Avoid submitting a duplicate bug report by checking to see if your problem is already a known problem or one of our most frequently reported bugs. The bug reporting guidelines explain how to write a useful bug report that results in your problem being fixed.

Note: Bug number references are included to provide more information about the specified issue or feature.


What's New
New Additions to the Release Notes
System Requirements
Compatibility Information
Installation Notes
Files Created or Used
Known Problems
Setting Profiles
Mail and News
ChatZilla IRC Client
JavaScript Debugger
International Release Notes
Quality Feedback Agent
A Note For Web Developers
How To Get Involved With Mozilla
Where To Find Other Builds

What's New in Mozilla 1.4 Beta

New Additions to the Release Notes

These are items that have been added to the release notes since the last milestone although the bugs themselves may have existed previously.

System Requirements








Compatibility Information

To use MathML in Mozilla, you must install the appropriate TeX fonts. See for information on installing the appropriate fonts. (Bug 134849)

Mac OS

If you attempt to run Mozilla on Mac OS using a language pack (such as the Japanese Language Pack) and a Language Kit, all menu bar items will be incorrectly displayed. To resolve this problem, register Mozilla using the Language Register. For instance, if you're using the Japanese Language Pack and the Japanese Language Kit, register Mozilla as a JA application.


When using a window manager from the twm family without the DecorateTransients option, pop-up windows such as Find, Save and Preferences will not function. To work around, set the DecorateTransients option in the window manager's rc file. (Bug 78928)

Installation Notes

Note: It is recommended that you uninstall previous versions of Mozilla before installing Mozilla 1.4 Beta. This will not delete your bookmarks, history, cookies and other information which is stored in your profile directory.

Windows Users: If you get the message, "uninstall.exe file is linked to missing export shell32.dll", delete %TEMP%\ns_temp.

Installing on Windows

It is strongly recommended that you exit all programs before running the setup program. Also, you should temporarily disable virus detection software.

To install Mozilla by downloading the Mozilla installer, follow these steps:

  1. Click the Mozilla-win32-installer.exe link to download the file to your machine.
  2. Navigate to where you downloaded the file and double click the Mozilla program icon on your machine to begin the Setup program.
  3. Follow the on-screen instructions in the setup program. The program starts automatically the first time.

To install Mozilla by downloading the .zip file and installing manually, follow these steps:

  1. Click the link or the link to download the .zip file to your machine.
  2. Navigate to where you downloaded the file and double click the compressed file. Note: This step assumes you already have a recent version of WinZip installed, and that you know how to use it. If not, you can get WinZip and information about the program at
  3. Extract the .zip file to a directory such as C:\Program Files\Mozilla 1.4b .
  4. To start Mozilla , navigate to the directory you extracted Mozilla to and double click the Mozilla.exe icon.

Installing on Mac OS X

To install Mozilla by downloading the Mozilla disk image, follow these steps:

  1. Click the mozilla-mac-MachO.dmg.gz link to download it to your machine. By default, the download file is downloaded to your desktop.
  2. Once you have downloaded the .dmg.gz file, drag it onto Stuffit Expander to decompress it. If the disk image doesn't mount automatically, double-click on the .dmg file to mount it. If that fails, and the file does not look like a disk image file, do a "Show Info" on the file, and, in the "Open with application" category, choose Disk Copy. In Mac OS 10.2, you can use "Open with" from the context menu.
  3. Once the disk image mounts, open it, and drag the Mozilla icon onto your hard disk.
  4. We recommend that you copy it to the Applications folder.
  5. Now Eject the disk image.
  6. If you like, you can drag Mozilla to your dock to have it easily accessible at all times. You might also wish to select Mozilla as your default browser in the Internet system preferences pane (under the Web tab).

Installing on Linux

You must run Mozilla at least once to complete autoregistration and for the compreg.dat file to be written to the installation directory. If a different user (other than the person who installed the product) runs the program first, a core dump will occur. (Bug 49345)

Note: To run Java applets, you must install the Java Run Time Environment (JRE) v1.3 plug-in.

Note: These instructions use the bash shell. If you're not using bash, adjust the commands accordingly.

To install Mozilla by downloading the Mozilla installer, follow these steps:

  1. Create a directory named mozilla1.4b (mkdir mozilla1.4b ) and change to that directory (cd mozilla1.4b ).
  2. Click the link to download the installer file (called Mozilla-i686-pc-linux-gnu-installer.tar.gz).
  3. Change to the Mozilla directory (cd mozilla1.4b ) and decompress the archive with the following command:
    gunzip -dc moz*.tar.gz | tar -xvf -
    (This places the installer in a subdirectory of Mozilla named mozilla-installer.)
  4. Change to the mozilla-installer directory (cd mozilla-installer) and run the installer with the ./mozilla-installer command.
  5. Follow the instructions in the install wizard for installing Mozilla.

    Note: If you have a slower machine, be aware that the installation may take some time. In this case, the installation progress may appear to hang indefinitely, even though the installation is still in process.
  6. To start Mozilla , change to the directory where you installed it and run the ./mozilla command.

To install Mozilla by downloading the .tar.gz archive file:

  1. Create a directory named "mozilla1.4b" (mkdir mozilla1.4b) and change to that directory (cd mozilla1.4b ).
  2. Click the link to download the non-installer mozilla*.tar.gz file into the mozilla1.4b directory.
  3. Change to the mozilla directory (cd mozilla1.4b ) and decompress the file with the following command:
    gunzip -dc moz*.tar.gz | tar -xvf - (This creates a "mozilla" subdirectory under your mozilla1.4b directory.)
  4. Change to the mozilla directory (cd mozilla).
  5. Run Mozilla with the ./mozilla run script.
Multi-user installs: To install Mozilla for multiple users on Unix, install as normal, then create the following script in your Mozilla directory, make it executable (chmod u+x <scriptname>), and run it as a user with write privileges to the mozilla directory (e.g. root). Do not run this program as su[do] root. (Bug 52653)
dist_bin=`dirname $0`
touch $dist_bin/chrome/user-skins.rdf $dist_bin/chrome/user-locales.rdf
You should then be able to run that installation of Mozilla as any user who has permissions to access it.

To hook up Mozilla complete with icon to the GNOME Panel, follow these steps:

  1. Click the GNOME Main Menu button, open the Panel menu, and then open the Add to Panel sub-menu and choose Launcher.
  2. Right click the icon for Mozilla on the Panel and enter the following command:


    where directory_name is the name of the directory you downloaded Mozilla to. For example, the default directory that Mozilla suggests is /usr/local/mozilla.
  3. Type in a name for the icon, and type in a comment if you wish.
  4. Click the icon button and type in the following as the icon's location:


    where directory_name is the directory where you installed Mozilla . For example, the default directory is /usr/local/mozilla/icons/mozicon50.xpm.

Installing RPM builds: The Red Hat RPM builds are created to work with the default Red Hat 6.x and Red Hat 7.x installations. Using these RPMs on SuSE requires installation of the gdk-pixbuf package. (Bug 85218)

Installing Address Book Palm Sync on Windows

To be able to sync between Mozilla's address book and your Palm, choose Address Book Palm Sync Install in the Mozilla group in the Start Programs menu. Note that if you set up your Palm to sync its address book with Mozilla, the address book will no longer sync with the Palm Desktop.

Once you have done this you can connect your Palm device and hit the HotSync button on your Palm cradle. This should bring up the HotSync Manager dialog on your desktop and should start Mozilla. Once sync is complete, close Mozilla and then restart it and open Mozilla Address Book to verify the sync.

Some Palm users may need to add an extra step to this process and add a registry key by hand.

  1. Download this registry key and save to your hard drive.
  2. If your Palm software is not installed in C:\Palm then edit the registry key file and set the proper path. Please make sure that the path you specify is within " " and for each directory separator use two ( use \\ for each \ ).
  3. Now go to Windows explorer and double click on this file. This should display a message saying "Information in this file has been successfully entered into the registry".
  4. Redo the Address Book Palm Sync Install to enable Mozilla Address Book Palm Sync.

Installing Java

Windows and Linux: To run Java applets, you must install the Java Run Time Environment (JRE) plug-in.
Windows: When using installer builds, everything should Just Work without any help.

See the Java section for more details about Java version compatibility.

Windows: If you're using the Installer build and you already have JRE 1.3.0_01 on your system Mozilla should recognize it. If you've manually set the pref to disable automatic plugin searches then you can do the following to get Java working: After the JRE is installed on your machine, copy NPOJI610.dll from the install directory (something like C:\Program Files\JavaSoft\JRE\1.3.0_01\bin) to your Mozilla plugins directory (something like C:\Program Files\ Mozilla 1.4b \bin\plugins).

Linux With tar.gz builds on Linux, after the JRE has installed, put a symlink to java2/plugin/i386/ns610/ in your mozilla1.4b plugins/ directory. (Note copying the file instead of making the symlink will cause Java to crash)

With Linux RPM builds, you must install Java as the root user.

Uninstalling Mozilla



Mac OS X

Files Created or Used

Mozilla stores data associated with you in a place called a profile. Profiles contain your preferences, mail folders, history, cookies, address books and other important data. Here is a list of these files.

Cache Cache files (temporary internet files). Enter about:cache in the URL bar for more information.
chrome User defined styles and installed themes and applications
ImapMailIMAP mail
MailLocal Folders and POP3 mail
NewsUsenet Newsgroups
somenumber.s Password data
somenumber.w Fill Form data
XPCOM Auto Registration clue. Tells Mozilla to check for newly installed components the next time it launches.
Application Registry. Files where Mozilla keeps track of your profiles.
abook.mab Personal addressbook
bookmarks.html Bookmarks
cert7.db Client Certificate database
Mozilla XPCOM registry. Files where Mozilla keeps track of its components.
cookies.txt Cookies
cookperm.txt Cookie and Image permissions
history.dat URL history
history.mab Collected Address book
key3.db Key database
localstore.rdf Defines default windows settings. Saved persistent values. Info about toolbars, size, positions, etc
downloads.rdf Download history
training.dat Junk Mail filter trainging data
mimeTypes.rdf Defines recognized file mime types for the Helper App
panacea.dat Mail folder cache. Summary of certain fields in all the mail/news databases, mostly used to display the folder pane
panels.rdf Information about which panels that will be displayed in the sidebar
prefs.js All your settings. Enter about:config in the URL bar for more information.
pluginreg.dat All your registered plugins. Enter about:plugins in the URL bar for more information.
search.rdf Information about your search plugins in the sidebar
secmod.db Security module database
URL.tbl Excluded Fill Form data sites
user.js User setting which will be written into prefs.js after Mozilla is started
xpti.dat XPCOM typelib information catalog
XUL FastLoad File
XUL fast load file. Contains precompiled chrome and JavaScript.
At some time Mozilla invalidated your XUL fast load file. These are the files. You can just delete them if you don't want to debug them.
(Windows) Stores component version
(Windows) Uninstaller executable file
Other Files
*.msf Mail Summary Files. Contains summary of the mail folder. Located in the ImapMail and Mail directories.
msgFilterRules.dat Contains the Mail Filters for the current server. Located in the ImapMail and Mail directories.
*.rc Contains subscribe newsgroups for the current server. Located in the News directory.
hostinfo.dat Contains all the newsgroups available for the current server. Located in the News directory.

Profile Locations

The following lists typical profile locations:


On Windows 95, Windows 98, or Windows ME (without log-in), the profile directory is typically
    C:\Windows\Application Data\Mozilla\Profiles\[User Profile]\[random string].slt\

On Windows 95, Windows 98 or Windows ME with log-in, the profile directory is typically
    C:\Windows\Profiles\[Log-in Name]\Application Data\Mozilla\Profiles\[User Profile]\[random string].slt\

On Windows 2000 or Windows XP, the profile directory is typically
    C:\Documents and Settings\[Log-in Name]\Application Data\Mozilla\Profiles\[User Profile]\[random string].slt\

Note: on Windows 2000 or Windows XP, the Document and Settings directory is hidden twice. To access the directory, enable Windows Explorer to view System and Hidden directories and files.

Mac OS X

The profile location is typically:
    ~/Library/Mozilla/Profiles/[Profile Name]/[random string].slt/


The profile location is typically:
    ~/.mozilla/[Profile Name]/[random string].slt/

Known Problems


Mac OS and Windows: Using ATI video drivers will lead to random crashes on many sites. Mac OS ATI driver versions affected: All (?) Windows ATI driver versions affected: (Mac OS) Workaround: set your screen to 'Thousands of colors' rather than 'Millions'. (Windows) Possible Workaround: Revert to an older driver (6094?)-- Untested (Bug 101055)

Keyboard and Mouse

Linux: Keyboard shortcuts on Linux now use Ctrl instead of Alt as the modifier key, while Alt is used for menu shortcuts. If you wish to modify these shortcut keys, add the following prefs (instructions here):

user_pref("ui.key.accelKey", 18);
(This changes the accelerator key from Ctrl (17) to Alt (18).)

user_pref("ui.key.menuAccessKey", 0);
(This changes the menu access key from Alt (18) to none.)

Linux: Clicking the middle mouse button in areas without links may lead to alerts popping up. (Bug 96972)

Event Handling

Wrong events are fired on FILE element. (Bug 4033)

Mouse wheel scrolling

Linux: You must have your X server properly configured to enable mousewheel scrolling. For XFree86, add a line to the Pointer section of your XF86Config files such as "ZAxisMapping 4 5". Also be sure that the Protocol line is set up correctly for your mouse.

Windows: Mousewheel scrolling does not work with all drivers. If you have problems, try updating your driver or disabling any "helper" programs that your mouse uses. If you have a Logitech mouse, you can either upgrade the driver (to at least v9.60) or enable the "Microsoft Office compatible scrolling" option in the Mouse/Buttons control panel. (Bug 33732)

Windows: old drivers of Synaptics touchpad may not have scrolling enabled for Mozilla. You can get a new driver at .

Mac OS: Mousewheel scrolling does not work with all drivers. If you have problems, try updating your driver or disabling any "helper" programs that your mouse uses.

Dialog Boxes and Windows

If Mozilla is locked up but doesn't seem to have crashed, make sure there are no dialog boxes still open. Close each window on your desktop one at a time and if you uncover a dialog window, dismiss it. If you have multiple desktops, repeat these steps for each desktop.

This problem may affect Linux users downloading plugins. Follow these steps to resolve the problem:

  1. Minimize the plugin download window.
  2. Click "Cancel" to dismiss the dialog box.
  3. Reopen the download window and continue downloading the plugin.

Form Manager

Form Manager is not fully implemented in the Japanese version of Mozilla .


Many Linux systems (in particular, Red Hat Linux systems) have bad Arial fonts. (Bug 46415) If many Web pages, especially those using the Arial font, look unclear, small, or hard to read, the following links explain two ways you can change your font server to get better Arial fonts:

If that doesn't work, you may be able to fix the problem by renaming or removing /usr/share/fonts/ISO8859-2. For instance, enter the following command:

mv /usr/share/fonts/ISO8859-2 /usr/share/fonts.ISO8859-2

and then log out of Linux and log back in again. You can always undo this, if necessary, by entering the following command:

mv /usr/share/fonts.ISO8859-2 /usr/share/fonts/ISO8859-2


Mozilla needs to be configured to work properly with proxies such as Junkbuster that do not support the most recent HTTP specification. By default, Mozilla tries to use HTTP 1.1. To use Mozilla with a proxy that only supports HTTP 1.0, change the HTTP Version from 1.1 to 1.0 in Edit | Preferences | Advanced | HTTP Networking | Proxy Connection Options. (Bug 38488)

Mozilla only accepts hostnames for manual proxies. If you migrate a Communicator 4 profile, you will need to change the settings manually. Communicator 4 allowed URL's in manual configuration, but Mozilla does not. If you migrate a profile configured this way, you will need to change the URL to a hostname and port number. (Bug 30387)

Setting Profiles

In Profile Manager, if you rename a profile to a name you previously used, all your preferences may be lost. Workaround: If you rename a profile, use a unique name. (Bug 113203)

To make a manual change to preferences, do not edit prefs.js. Create a new text file, user.js, in the same directory as prefs.js. Entries in user.js will override entries in prefs.js, if necessary. (Bug 142590)

If you have a single profile from Communicator version 4.5 or later, that profile is automatically copied and converted for use with Mozilla . Profiles from earlier Netscape versions cannot be converted.

If you have multiple profiles to copy and convert, the profile manager dialog box appears. Click the profile you want to use and then click Start.

If problems occur during installation and your Communicator profile was not copied and converted, you can still use your profile. Launch Mozilla from the command line, adding the "-installer" option (that is, type "mozilla.exe -installer" on the command line) , or reinstall Mozilla to see the profile manager dialog again.


Using Windows 98 with some ATI graphics adapters will result in occasional corruption of inline images as rendered on web pages. This is an ATI graphics driver bug. (Bug 104992)

If a username or password is embedded into a URI in the form of Mozilla will not warn the user of this when the user follows the link. URI's with long usernames in the form of could deceive users into thinking they were going to when they were really going to (Bug 122445)

If the user is downloading a file in the background and the user exits from the File menu, the download will abort without warning. Workaround: Only exit after downloads finish. (Bug 28385)

URLs using telnet:// do not work in Linux (and other UNIX systems). telnet:// URLs work for Win32 and MacOS. Workaround: Install protozilla. (Bug 194325)

When browsing with many tabs open (more than 25), some tabs may stop responding. Workaround: use multiple browser windows.

Additional Internet Search Engines can be obtained at

The "View Frame Source" feature is not available from the View menu; however, it is available in the context menu. To see the context menu, click the left mouse button to put the mouse pointer in the frame and then click the right mouse button (Control click on the Mac OS). (Bug 47139)

Pages that appear to be rendered incorrectly may be due to standards compliance issues. See the Netscape DevEdge and Mozilla Evangelism sites for more details.

Accessing Pages

While enabling HTTP pipelining may significantly improve page load times, it can prevent some websites from loading correctly. If you experience problems loading a website, please verify that HTTP pipelining is disabled and try again (see Preferences->Advanced->HTTP Networking). HTTP pipelining is disabled by default. (Bug 144607)

Mozilla may not be able to connect to some secure (HTTPS) IBM Web servers. This is a problem with the servers' software, not with Mozilla . (Bug 54031)

If you use "Last page visited" as your Home (starting) page, if the last page you viewed had frames, it may not be displayed correctly when you next restart Mozilla . (Bug 58613)

Accessing pages with a Uniform Naming Convention (UNC) requires 5 slashes (file://///). (Bug 66194)

Linux: On Linux, there may be problems with ESD Audio and Flash. (Bug 85772)

Downloading Files

Hourglass cursor, progress meter, and throbber do not stop spinning although downloading has been finished. Status bar says "Transferring data from ..." when page is done loading. (Bug 39310)

If you're unable to remove user-defined helper applications try the following:
  1. Open the Edit menu, and choose Preferences. Choose Helper Applications within the Navigator category.
  2. Select the helper application/mimetype you wish to remove from the list, and click the Remove button.
  3. Click OK to confirm.
  4. Click OK to dismiss the Preferences dialog box.
  5. Quit completely and restart Mozilla .


Bookmarks cannot be rearranged if you have sorted them. To rearrange them, select Unsorted from the View menu, or click the Name column header until the arrow disappears. (Bug 64768)

View Source

Mac OS: The horizontal scrollbar in the View Source window might be missing. Resize the window to see the scrollbar. (Bug 56488)

Mail and News

Moving or copying a labeled message will not retain label in destination when filing across accounts:

  1. IMAP to any other account (including Local Folders): Message labels are lost.
  2. POP to POP (including Local Folders) is OKAY.
  3. POP to IMAP: Message labels are lost.
  4. Copy Newsgroup messages to any account: Message labels are lost. (Bug 133795)

In the Mail/News Account Settings: Server Settings dialog box, any changes you make to local directory settings won't take effect until you exit and restart Mozilla . (Bug 2654)

Mozilla does not warn the user of a low disk space condition. (Bugs 32443, 56565) Some symptoms you may see are:

Mail account identity is not stored along with an unsent message. (Bug 59548)

Linux: You may encounter problems if you install Mozilla in a root user environment then run as another user. Problems include saving to Sent folder, Drafts, Templates or general authentication problems. (Bug 49397)

The Mail & Newsgroups Account Settings dialog box does not display correctly at lower monitor resolutions such as 800 by 600 or 640 by 480. If possible, increase your monitor's display resolution above 800 by 600. (Bug 82122)


SMTP over SSL often doesn't work to port 465 (the standard secure SMTP port), or any port other than 25, due to a protocol (STARTTLS) handling problem. Workaround: Use port 25, and the connection should work and still be secure if you choose 'always' or 'if available'. Otherwise, Mozilla will hang. (Bug 98399)

AOL Mail and Netscape WebMail Accounts

Mozilla does not integrate with AOL Mail and Netscape WebMail, as Netscape 6/7 do. If you share your Netscape 6/7 profile with Mozilla, you may be able to see headers for messages in the account's Inbox if you have previously checked one of these accounts in Netscape 6/7, but you will be unable to interact with the messages. To access your AOL Mail, WebMail, or Netscape Instant Messenger, you need to use Netscape 6/7.

Receiving and Reading Messages

You may not see the message header (From, Subject, Date, To, Cc, and so forth) when you read messages. This problem often occurs when you switch mail folders or newsgroups. To see headers, resize the window or the message content pane. (Bug 39655)


In some cases you can't view more than one HTML/Web page attachment to a message in the mail window. The attachments will not all be shown or you may experience a crash when attempting to display them. (Bug 38398)

Attaching RTF files to emails may result in them being sent such that most readers will not be able to read them. If you plan to send RTF attachments, you should go to Edit>Preferences>Navigator>Helper Applications, select "New Type", and enter:

MIME Type: application/rtf
Description: Rich Text Document
Extension: rtf
and then select OK to close the dialogs.

Address Book

Imported Netscape Communicator address books appear in Mozilla as a separate address books. (Bug 41590)

To import Outlook address books, you must have the default mail client set to "Microsoft Outlook" in Microsoft Internet Explorer. Do this:

1. Launch Internet Explorer.
2. Click Tools in menu bar, then click Internet Options. The Internet Options dialog box appears.
3. Click the Programs tab and select "Microsoft Outlook" as the default e-mail client.
4. Hit OK and exit Explorer. (Bug 90206)

(Windows) You may need to try more than once before Outlook Express address books are imported successfully. (Bug 90206)

Copying a large number of addresses between address books may cause crash. (Bug 82991)


If you have multiple filters configured for a mail account, incoming messages will continue to be evaluated against each filter (in the order listed in the Message Filters dialog) until a filter action of Move to Folder or Delete is executed. This differs from Communicator 4.x where any filter action would stop further filtering on a message. (Bug 30081)

Pop and IMAP

You must exit and restart Mozilla to see the effect of a change to the option: "show All IMAP mail folders" or "show only subscribed IMAP mail folders." To access this option: click the Advanced button in the Server section of the Account Settings dialog box. (Bug 38943)


The Subscribe dialog box may not work with news servers that require authentication. If you open a password-protected newsgroup you may be prompted more than once for the user name and password combination.


LDAP directories with ldif extensions may appear after migration from Communicator 4.x. (Bug 94645)

Mozilla may temporarily hang during LDAP autocomplete if network connectivity is broken. Specifically, if the LDAP server in question is unreachable (network connectivity problems, including taking a laptop outside a firewall), the entire app will hang when attempting to contact that browser. The app will begin responding again after about 10 seconds (the length of the TCP timeout). (Bug 79509)

Offline Mail

Moving/Copying a downloaded message (while offline) will result in not being able to read the message at the new folder while you are offline. Workaround: Go online to read it, then re-download the message to have it accessible when you are offline. (Bug 78809)

When starting Mozilla, if you only have one profile, both of the Offline preferences for startup mode ("Ask me if I want online or offline mode", or "Use my previous online/offline state") do not work. Mozilla will always start in online mode. To go offline, from the File menu, choose Work Offline. (Bug 82487)

If the user starts Mozilla in offline mode (clicking the work offline checkbox in the profile manager), then tries to reply to a message while in offline mode, or double clicks on a message (which brings it up in a separate window), in some instances the application might crash. (Bug 92368)



ChatZilla is not finished, but is usable if you're willing to accept a subset of the commands offered in more mature IRC clients. A large percentage of ChatZilla users experience crashes, odd behavior, rash, shortness of breath, and an urge to fix bugs. If you would like to contribute, please tell us in the netscape.public.mozilla.rt-messaging newsgroup, or send an e-mail to

If you are not familiar with IRC, please check out the FAQs available at

Running ChatZilla

Start Mozilla with the -chat option to start ChatZilla, or select it from the Window menu.

More Info About ChatZilla

See the ChatZilla User's Guide for information on using ChatZilla. For info on building ChatZilla, click here. (Note that ChatZilla builds automatically on Windows and Mac OS).

JavaScript Debugger

Once you've floated all the views out of the main window, no drop targets remain to bring them back. If you have "Save Default Layout On Exit" checked, and you exit, you will appear to be stuck like this. (Bug 151785)

As a workaround, show the Interactive Session from the Show->View/ Hide menu, and type "restore-layout factory".


When Publishing in Composer, if the Publishing URL, file name, user name, or password contain any special characters (such as "@") that need to be escaped, then Composer creates a duplicate site entry each time you publish the document. To work around this bug, choose the original site name from the Site Name list in the Publish dialog box before publishing the document again. For example, some ISP users have usernames that are also their email addresses, e.g., "". After publishing to this site, the next time you use the Publish dialog, the username from the document URL will appear as "" (the "@" was escaped during publishing). Since Composer can't find this entry, it creates a duplicate site name. (Bug 141819)

You may not be able to simultaneously edit a document using both Composer and another editor. (Bug 37089)

You can't apply a font style across paragraphs and images. Font changes must be done within each paragraph.

Applying a font style across several words yields multiple font tags in the HTML code.

When the background color on a page is set, only the frames behind the lines of selected text are colored. Resizing the window triggers the proper repaint.

After applying a color to text, the text may appear partially highlighted.

Certain pages (such as ones that set frames) can't be edited. However, you are still able to choose the Edit Page option in the File menu for such pages. An editor window opens, but you are unable to edit the page.

Edit|PasteAs function is not functioning. (Bugs 73286, 41547)

File|Open Web Location, selecting to render in Composer does not open document in Composer. (Bug 71426)

You can not print HTML Source. (Bug 82239)

Numerous shortcut keys do not function properly. (Bugs 26264, 48951, 57805, 70630, 26269, 53505, 76925, 57700, 67142, 48375)

Hourglass does not show when application is busy. (Bug 83300)

Some element icons do not render in Show All Tags mode. (Bug 88036)

List editing can cause nested lists to outdent to next level list. (Bug 98547)

Remove option from personal spell check dictionary does not work. (Bug 43348)

If the cache preference is set to "Every time I view the page" and a new document is created, toolbar icons may be disabled on the toolbar and the caret may be missing. Workaround: Do not set the cache preference to "Every time I view the page." (Bug 97633)


When visiting a SSL enabled site, the lock icon will take on a yellow background, and will not indicate the strength of the SSL encryption used, whether it is 40 bit, 56 bit, or 128 bit. (Bug 74320)

Restoring a certificate to a smart card can take a long time. No feedback is provided while restoring a certificate to a smart card, which can take a long time since smart cards are relatively slow devices. As a result, it may appear that the restoration is not happening. (Bug 52321)

For security reasons, Mozilla does not allow connections to certain ports. To override this on a per-port basis, add a comma separated list of ports to defaults/all.js (in your Mozilla installation directory). Note that this pref only works in the all.js file in the Mozilla installation directory and it affects all users of the installation. It does not work if you add it to the prefs.js or user.js files in your personal profile directory. For example, to unblock ports 1, 3, and 7, use the following line:

pref("", "1,3,7");

For security reasons, Mozilla does not allow web content to link to local files. An error like: Security Error: Content at url may not load or link to file:///something will appear in the javascript console. If you need to follow links to local paths it is recommended that you drag the link to the location bar and then drop it on the webpage. If you really don't like the security check and are willing to risk all files on your system and that your system can access then you may add the following line to user.js in your personal profile directory. (Bug 84128

user_pref("security.checkloaduri", false);

Windows: Some software firewalls may block Mozilla from properly accessing the Internet. If Mozilla is not working properly, check that your firewall settings allows Mozilla to connect to the net. If your receive a warning from ZoneAlaram that Mozilla attempts to set itself up as a local server, it is due to Mozilla communicating with Personal Security Manager (PSM) which is required to access secure Web and mail servers, and you should allow Mozilla access.


Do not share a profile between Netscape and Mozilla nightly builds. Doing this can lead to unpredictable results, some of which may include loss of Search settings and preferences and unchecked growth of the Bookmarks file (large enough to freeze your system). It is best to create a new profile for each or manually copy (and change the name) an existing profile. (Bug 137164)

If you are using the Classic theme, some preference panels may be displayed incorrectly or may have missing elements. If you view a different preference panel and then return to the one you're working in, the display is corrected. (Bug 51241)

Preferences window initial size doesn't always give hints on all options available. Resize the window from its lower right corner to see them all. (Bug 53375)


When you close the last window, Mozilla will unload itself and reload itself this may take a while. This will probably result in lots of disk thrashing. (Bug 143764)

When you close the last window, the icon in the tray will disappear and reappear at the end of the tray. (Bug 146340)


For more information on plug-ins, see the plugin doc at

Windows: The Adobe SVG plugin crashes. Workaround: Don't copy it (NPSVG3.dll into your plugins folder. If you want to view SVGs, there are Mozilla builds with native SVG support. (Bug 133567)

Linux: The Flash plugin context menu does not disappear when you click outside the plugin area to dismiss it. Workaround: Click inside the plugin to dismiss the plugin context menu. (Bug 63182)

Linux: Mozilla crashes while playing Flash content on a remote X display. No workaround present other than not using remote X display. (Bug 58937)

Linux: Loading a page that contains a Flash plugin may cause Mozilla to lock up if you are using an audio application. (Bug 58339)

Plugins installed for Communicator 4.x may not be available for Mozilla . Workaround: install these plugins in the Mozilla Plugins folder.

Windows: Microsoft Media Player file embedded in web pages may not work. (Bug 66015)

Mac OS: Mozilla now scans for plugins in the system's "Internet Plugins Folder" first.


In Print Preview, plugins are not shown. (Bug 134002)

Windows: Some users might not be able to print on Windows 98 or Windows ME with the default spool setting. The workaround is to go into printer properties, choose details tab, choose spool settings, and then choose print directly to printer. (Bug 130083)

Linux: There are several bugs with the default PostScript module that are not present in the optional Xprint module. (buglist).
Some print preview functionality is only available with the Xprint module which is not the default printing module. (buglist)

Mac OS and Linux: Transparent backgrounds are printed as black. (Bug 137114, 137115)


When going to a site that requires the user to authenticate with HTTP to download a Java applet that also requires authentication, the user will have to login twice with the same username and password. (Bug 60304)

Java J2SE releases previous to 1.3.0_01 will not work with Mozilla. Problems have been reported with JRE 1.3.1. For best results JRE 1.4.1 is recommended. Mozilla has been tested with all 1.3.0_* versions of the JRE, and JRE 1.3.1, and beta versions of JDK 1.4.

Running J2SE in 256 color mode may cause a flickering problem.

Linux: LiveConnect support now works if you use Mozilla 1.4 Beta with JRE 1.3.1. Additional LiveConnect problems are being addressed in JDK 1.4 as mentioned above.

Sun's JRE will crash at startup if your useragent does not begin with Mozilla/5. It might print

Expected a version > 5! Version = 4

The workaround is to not forge a useragent whose version is less than 5 if you have the Sun JRE plugin in your plugin directory. this preference would appear in pref.js as something like:

user_pref("general.useragent.override", "Mozilla/4.0 (compatible; MSIE 5.0; Windows 98;)");
(Bug 83376)

If Java doesn't work, make sure the following is true:
On Windows:
Copy the NPOJI610.DLL from C:\JDK*\jre\bin to "\plugins" directory of your installation.
On Unix:
Make a symlink to /usr/java/j*/jre/plugins/i386/ns610/ in your mozilla1.4b plugins/ directory. Do not copy the file, but instead make a symlink to it.

International Release Notes


Mozilla has been designed to display many different languages without extra steps. The user should be able to browse and use e-mail without complicated setups or efforts when necessary fonts are available on the system.

Mozilla can be used with more than one language pack, which lets the user change the menu language and relevant URLs.

Contents of Sidebar tab and Bookmark will not change when you choose another region -- they are bound to a specific profile. (Bug 87939)

If you are using Chinese, Korean or Japanese language Windows 9x/ME and launching fails or crashes, read the Java section of the Known issues section below for possible causes.

You may be unable to print out Japanese characters from Win98-J with HP Laser Jet driver (Japanese version). Workaround: Install the driver that comes with the Japanese Windows 98 installation CD. (Bug 86989 )

If you have WinME-Ja, you may not be able to print to a HP LaserJet 5Si/5Si MX using the HP LaserJet 5Si/5Si MX PS printer driver In this case, you should change the driver to HP LaserJet 5Si/MX. (Bug 86989)

New: On platforms which support file names in Unicode, it is possible to create files and folders bearing names in scripts which fall outside of the system locale. Browser operations which involve such folder or file names may not succeed, e.g. saving into such a folder, or opening a file whose path contains such characters. Using only characters supported by the default system language avoids this type of problems. (Bugs 58866, 100243, 100344, 100364, 100396, 101573, 128380, 104305)

General and Profile Manager

On Japanese Windows XP, the desktop icon and Mozilla Program Folder cannot be removed after Mozilla program is removed through a program uninstallation via the Control Panel. You can manually remove them. (Bug 125104)

Navigator and Composer

Mozilla does not support Dynamic Fonts. (Note: It was supported in Communicator 4.x.)

Auto-detect All/Universal may not be able to detect encodings on pages which don't supply document encoding information. You can increase the accuracy if you choose other auto-detection modules with a smaller scope for detection , e.g. Chinese, Simplified Chinese, East Asian.

With the Windows 2000 IME, most of the new Japanese IME features (e.g. reconversion) are supported but some features may not work correctly. (Bugs 18680,

Support for the Unicode surrogate range is not currently available for Linux. (Bug 127713.)

A Composer page cannot be saved into ISO-2022-KR using the Save As ... menu because there is no converter available from Unicode to ISO-2022-KR. ISO-2022-KR will be eventually hidden in the Save as .. menu. (Bugs 132070 and 133615.)

When opening a file under a folder with multi-byte folder name, the path name in multi-byte characters is escaped in the title bar of Composer window. (Bug 136221.)

Linux only: Bold and Italics styles may not work on ASCII characters when editing a CJK page. This is most likely to happen on CJK locales without good ASCII fonts. For example, you may be using language open-source CJK locale support files. On commercial Linux distribution, particularly recent ones, the support files contain better CJK fonts and this problem is less likely to occur. (Bug 91145)

Mac OS: Non-ASCII non-Latin 1 info stored in Internet Config will not show correctly in auto-fill fields such as "Your name" field in the Mail account setup dialog. If this happens, you can manually correct auto-filled entries. (Bug 5721)


Filtering by body key is not implemented.

The Character Coding menu cannot correct the thread pane display of non-MIME encoded headers. This is by design. If the message displayed lacks MIME charset information, the thread pane display obeys the default message display charset set via the folder properties dialog (set via the menu Edit | Folder Properties ...). Correctly setting this option to the charset most often used in the user's mail viewing helps avoid display problems of this type


Some cases have been reported in which Windows 9x/ME Japanese users have a problem starting Mozilla when there is a prior installation of older JDK or JRE under the operating system in use. The JRE 130_02 (or later) that Mozilla users can download from a Netscape ftp site contains many fixes since the official release of JRE 1.3. If you are using an older version of JRE 1.3 or the US version of JRE 1.3 under Japanese/Chinese/Korean Windows, you may experience this non-start problem.

To determine if the non-starting problem is due to Java installation, follow these steps:

  1. Locate the Plugins directory (which is found in the same directory as the Mozilla executable).
  2. Remove all the Java plugin files from the Plugins directory, i.e. the files whose names begin with "npjava...". Remove also the NPOJI610.dll file if you find one. Back them up in another directory so that you can restore them later.
  3. Restart Mozilla . If Mozilla starts, then you have a Java related non-start problem.

If you have the Java problem as described above or want to install updated JRE 130_02 (or later) that you can download from a Netscape ftp site, follow these steps (Note: This type of problem has not been reported for Windows NT4/2000, but if you experience this problem on the latter two platforms, follow these steps for those platforms also):

  1. Click the Start button, open the Settings menu, and choose Control Panel.
  2. Double click the Add/Remove Programs icon and select the Install/Uninstall tab.
  3. Locate the old JRE installation (Java Runtime Environment) and delete it.
  4. After the old JRE has been deleted, run Mozilla again, and go to any site that requires the use of Java. You will see a plugin-in icon on such pages telling you to click on the icon to download a Java Plugin.
  5. When you click on the "get Java Plugin" icon, you will be taken to a Netscape site to download a Mozilla plugin.
  6. Download the "International" version if you would like display of international characters. (recommended)
  7. Follow the instruction for the installer and complete Java 2 installation.

Mac OS and Linux: Display of non-ASCII characters (particularly Chinese/Korean/Japanese) in applets may not work without correct font settings in files. Windows releases ship with modified files. This document may be helpful to Mac and Linux users.

Quality Feedback Agent

Quality Feedback Agent collects data about Mozilla in the event of a crash. Such information helps Mozilla developers to quickly isolate the cause of a crash and then correct it. The software does not collect any sensitive information such as Web sites visited and passwords. Reporting crash data is one of many ways in which users can help improve the quality of the software. Participation is not required but highly recommanded.

On Windows, if you are using automatic proxy configuration, you need to edit your talkback.ini file for Quality Feedback Agent to work.

Setting User Preferences using user.js

Mozilla is very configurable, however there is not room in the UI for controls to change all the preferences. If you need to change a preference for which there is no UI, you will need to edit your preferences file, user.js. These instructions detail how to do this.

This file is read in by Mozilla when it loads your profile, so if you modify the file while Mozilla is running, your changes will not take effect until you restart Mozilla. If there is not already a user.js file in your profile directory, create it and then add the correct line or lines, which should have the form:

user_pref("", "somevalue");
user_pref("", true);

for on/off preferences. When you have finished editing, restart Mozilla.

Notes For Web Developers

For a list of known issues with support for Web standards (HTML 4.01, CSS1/2, DOM1/ 2, XML, RDF), JavaScript, Java, and Plug-ins in Mozilla, see the following documents:

When a page rendered in full standards or almost standards mode links to an external style sheet (using <link>, @import, etc.), Mozilla will load the style sheet only if it is served with a MIME type of "text/css". Style sheets served with other MIME types, like text/plain, application/x-pointplus, etc. will not be loaded. To add the proper CSS MIME type to an Apache web servers, add "text/css css" to the system mime.types file. Or if you can't do that, add "AddType text/css .css" to your .htaccess file.

How To Get Involved With Mozilla

Where To Find Other Builds