Mozilla[tm] 1.2.1 for Solaris[tm] Operating System Release Notes


This page provides release notes for Mozilla 1.2.1  for Solaris Operating System. This page contains the following sections:

Contents

Installation Notes

Runtime Issues

Internationalization Issues

Function Issue

Late-Breaking News

Documentation

Patch List

1. Installation Notes

You can find installation instructions at the following location:
 (http://www.sun.com/software/solaris/mozilla) or README file in your Mozilla 1.2.1 for Solaris package

Main points about the installation:

* You need 160 Mbytes disk space to install the Mozilla 1.2.1 for Solaris SVR4 packages.
* The /usr/sfw/lib/mozilla directory is the default directory for SVR4 packages installation.
* You must be root to install the Mozilla 1.2.1 for Solaris SVR4 packages.
* Java 2 Standard Edition 1.4.2 (J2SE) is highly recommended.
* You must have GTK2 Library or GNOME 2 Desktop (including GTK2 Library) installed.

Using previous versions of the J2SE may experience some compatibility
issues. For more information on the Java platform compatibility with previous releases please visit:
http://java.sun.com/j2se/1.4.2/compatibility.html

Checkpatches Script

At the beginning of the Mozilla 1.2.1 for Solaris installation process, the checkpatches.sh script runs to determine if all required patches are installed. If there are any patches missing, the script generates a list of the missing patches and prompts you to continue or stop the installation process. You should perform the following steps:

1. Stop the installation process.
2. Download the required patches from the download page.
3. Execute the patchadd command for each missing patch. If you attempt to add a patch that is older than a previously installed patch, a message informs you of the status. In this situation, you do not need to install the required patch.
4. When you have installed all the required patches, you can restart the Mozilla 1.2.1 for Solaris installation process.

To Uninstall Mozilla 1.2.1 for Solaris

Perform the following actions to uninstall Mozilla 1.2.1 for Solaris:
Note: You must remove optional packages separately.

If you installed Mozilla 1.2.1 for Solaris with SVR4 package, it will be uninstalled automatically when you install a new version of Mozilla with SVR4 package. Or, you can remove it using pkgrm.


If you installed Mozilla 1.2.1 for Solaris with Webstart, run:
% cd <installation directory name>
% ./uninstaller

Set Mozilla 1.2.1 for Solaris as the Default Browser

As for CDE desktop, perform the following actions to set Mozilla 1.2.1 for Solaris as the default browser:
1. Find "typeset bList="${2:-netscape sdthotjava hotjava }" in /usr/dt/bin/sdtwebclient;
2. Add mozilla to this list, "typeset bList="${2:-mozilla netscape sdthotjava hotjava}"
3. Add the following line into /usr/dt/bin/sdtwebclient before line 89
        BROWSER="mozilla"

As for GNOME desktop, just modify /usr/share/gnome/mime-info/solaris-gnome2.0.keys        
line 96: default_application_id=netscape-launcher -> mozilla

And perform the following line to add mozilla into your PATH.
ln -s /usr/dt/bin/mozilla /usr/sfw/lib/mozilla/mozilla


Share Plugins between Mozilla Installations

Plugins can be shared by different version of mozilla by setting MOZ_PLUGIN_PATH environment variable. Mozilla will check this environment variable to search plugins.

Theme Support

Please do not share themes between different versions of mozilla,  because neither backword compatibility nor forward compatibility of theme is supported. For example, themes for Mozilla1.2.1 may not work for Mozilla1.4, and vice versa.

2. Mozilla Runtime Issues

Debug Messages

You can generate debug messages to help you troubleshoot an application crash.

Action:

In the event of an application crash, restart Mozilla 1.2.1 for Solaris by typing
the following command in a Terminal window:

% mozilla -debug

Debug messages appear in the Terminal window in which Mozilla 1.2.1 for Solaris has
been started. These messages provide valuable information.

Java[tm] Plug-in Proxy Settings

If you set the proxy setting in Java Plug-in to use the Mozilla 1.2.1 for Solaris browser settings, then the Manual proxy settings of the browser are always used. If you set the browser to Direct connection to the Internet, Java Plug-in still uses the Manual proxy settings of the browser. The use of these proxy settings is only an issue with pages that contain applets.

Action:

The workaround is to uncheck the Java Plug-in proxy setting so that you do not use the browser settings. Peform the following steps:
1. Change to the following directory:
% cd <installation directory>/java/bin
2. Run the following command:
% ./ControlPanel
3. Click the Proxies tab
4. Uncheck Use browser settings
5. Click Apply
6. Close the window

Plug-in Focus Issue

When you are viewing pages containing plug-in with Mozilla 1.2.1 for Soalris, Mozilla may crash or can not catch the keyborad event due to plug-in focus iuuse. For example, dragging the Choice item of java component sometimes make mozilla crash. Or, can't input character into the java text field or area.

For more information, please see bugtraq: 4802104,4805571,4806234. This problem is been working on and will be resolved soon.

Ctl Issue

Mozilla 1.2.1 for Solaris will not support ctl (ctl means Complex Script support).
Reproduce steps:
1. open mailnews and compose a mail using html format
2. type a paragraph without hit return which can be automaticly wrapped into more than one line.
3. use left arrow key to move back

Expect result is that the caret moves back. But in fact, the caret runs to some unexpect place ( for example, directly to the behind of the 5th charact of the first line).

For more information, please see bugtraq 4801416. This bug is been working on.

Switching to CDE Fonts on Mozilla

1. Put user preferences in your ~/.mozilla/default/prefs.js file:

user_pref("font.name.monospace.x-western", "b&h-lucida sans typewriter-iso8859-1");
user_pref("font.name.sans-serif.x-western", "b&h-lucida sans-iso8859-1");
user_pref("font.name.serif.x-western", "b&h-lucida bright-iso8859-1");

You can also specify these preferences in the <installed-directory>/defaults/pref/unix.js file:

pref("font.name.monospace.x-western", "b&h-lucida sans typewriter-iso8859-1");
pref("font.name.sans-serif.x-western", "b&h-lucida sans-iso8859-1");
pref("font.name.serif.x-western", "b&h-lucida bright-iso8859-1");

It would be better to specify dt-.... styles here.

2. Modify global.css to specify sans-serif in font family in <installed-directory>/chrome/skin/modern/global/global.css as follows:

window
{
...
font family : sans-serif;
...
}

When you think the font is too small, please add font size as well.

font size : 14px;

This problem has already been reported as Bugid 5236 in bugzilla.

3.Modify css files to specify `inherit' for font family in

skin/modern/global/menulist.css: font family: geneva, arial;
skin/modern/global/tabcontrol.css: font family:charcoal, ms sans serif;
skin/modern/communicator/button.css: font:11px arial;
skin/modern/communicator/button.css: font family:Arial, sans-serif;
skin/modern/aim/findAFriendWizard.css: font family:serif;
skin/modern/aim/findAFriendWizard.css: font family:serif;
skin/modern/global/button.css: font family:charcoal, ms sans serif;

Tip for Improving Graphics Performance

Mozilla 1.2.1 for Solaris uses the GTK2 graphics library in Solaris for graphics operations. This library uses a considerable amount of shared memory. You can achieve better graphics performance by adding the following lines to your /etc/system file:

set shmsys:shminfo_shmmax = 0x2000000
set shmsys:shminfo_shmmni = 0x1000
set shmsys:shminfo_shmseg = 0x100

Note: You need to have root access to your machine to edit your /etc/system file. After you make this change, you must reboot your machine.


Profile Compatibility

If you have used a previous version of Netscape or Mozilla, you may experience problems due to incompatible preferences. It is recommended that you move your existing $HOME/.mozilla directory aside (e.g. % mv $HOME/.mozilla $HOME/.mozilla-old) before first time you starting Mozilla 1.2.1.

Please don't share the Mozilla 1.2.1's profile with other Sun-not-supported Web browsers, especially the nightly Mozilla builds from Mozilla.org community. Otherwise your profiles would got changed, even corrupted.

There are many causes result in the damages, even corruption, of mozilla profile, during the installation/migration and during daily using, including abnormal quitting of Desktop, mozilla crashing and sharing the same profile with other Sun-not-support Web browsers, especially the nightly mozilla builds from Mozilla.org community.

The following are some steps to get most of the important information back when mozilla profile got corrupted.

1: Quit Mozilla completely, make a backup for mozilla profile.
cp -r ~/.mozilla ~/.mozilla.bak

2: Delete following files:

localstore.rdf: ~/.mozilla/(AccountName)/*.slt/localstore.rdf
XUL.mfasl: ~/.mozilla/(AccountName)/*.slt/XUL.mfasl
appreg: ~/.mozilla/appreg

3: restart mozilla
If mozilla start smoothly, then turn to next step. Otherwise, remove prefs.js and try again.

prefs.js ~/.mozilla/(AccountName)/*.slt/prefs.js

If mozilla start smoothly now, then turn to next step. Otherwise, make a tarball of mozilla profile:

tar zcvf mozilla-profile.tar.gz ~/.mozilla.bak

and report a bug to mozilla-feedback@sun.com with the tarball as attachment.

4: Consequences of deleting and Get all of accounts back

I. localstore.rdf:
If localstore.rdf is missing on startup, a default version of it is created. Various browser appearance settings get a little confused then. The mailnews settings for columns to display are also forgotten, so you must de-select those you don't want displayed there.

To reset browser appearances: Start Mozilla, open File/Preferences. Check ALL the buttons you can possibly add to the interface under "Navigator", and click OK. Now open preferences AGAIN. Uncheck all you don't want displayed, and click OK.

II. XUL.mfasl:
Deleting XUL.mfasl doesn't cause any havoc. It's a "fastloader" for XUL. If the file is missing, it is simply recreated on next startup.

III. appreg:
Deleting appreg is slightly tricky. After deletion, Mozilla loose track of your profile on the next startup. But fear not, you can get them back with following steps.
-Start Mozilla
mozilla -ProfileManager
-In the next window, click "Create Profile..."
-In the popup, click "Next" button
-and under "Enter New Profile Name" add the exact name of your OLD profile directory (found right under ~/.mozilla). This is by default called "Default Profile".
-Then click the "Finish" button and then button labeled "Start Mozilla"
-If you have more than one user account, re-create all of them before click on button "Start Mozilla"

IV. prefs.js
Similar to localstore.rdf, prefs.js keeps some user-customized preferences of Mozilla, including browser and mail. If prefs.js is missing, you need to re-set your preferences again in Preference Dialog.


3. Internationalization Issues

This version of Mozilla does not support scripts that require Bidi (Bi-Directional) orientation such as Arabic and Hebrew.

Input Issue

It is very slow to open new window and move focus between Mozilla in UTF-8 (it has been fixed in Solaris 10) locale (Bug 4643078) This is a Solaris bug, not a Mozilla bug. It is fixed in Solaris 10. In multi-input mode on UTF-8 locale, it is very slow to change focus and open new window.
Workaround: Use non multi-input mode if possible.

Printing Issue

Printing does not work for non iso-8859-1 characters.
Printing does not work for non iso-8859-1 characters. All non iso-8859-1 characters are printed as square. (Bug 4474533)
Workaround: Try Xprint printing.

How to use Xprint on Mozilla 1.2.1 for Solaris
start Xprt server on your host. You would need to set additional font path, which depends on your locale. Please refer Xprt(1) for Xprt.
% /usr/openwin/bin/Xprt :1
Set XPSERVERLIST environment variable
% setenv XPSERVERLIST :1
Start Mozilla
% mozilla

In the print dialog box, enter your printer name into "Print Command:" text field, then click "Print" button

Displaying Issue

Problems with displaying chinese characters

There are some bugs of displaying chinese characters. Some code points below are not displayed, some are displayed as '?'.

zh_HK.BIG5HK locale: 0xF9DD - 0xF9FE display as space.
(bugtraq 4637808, see also: http://bugzilla.mozilla.org/show_bug.cgi?id=125412)
zh_TW locale: 0xC2A1 - 0xC2C1 (bugtraq 4637806)
zh_TW.BIG5 locale: 0xA3C0 - 0xA3E0 (bugtraq 4637805)
0xA27E - 0xA2A7 (bug 4637804, http://bugzilla.mozilla.org/show_bug.cgi?id=125406)


4. Function Issues

Roaming

Roaming is included in Netscape 4.x but not in the Netscape 6/7 and Mozilla product line. The project team plans on re-implementing roaming in the Mozilla code base although Mozilla and Netscape 4.x are from two different code bases. (Please see: http://bugzilla.mozilla.org/show_bug.cgi?id=17048)

AIM

Netscape 7 contains AOL's Instant Messaging (AIM) in the product. But Mozilla doesn't bundle AIM.

5. Late-Breaking News

For last-minute issues and information about Mozilla 1.2.1 for Solaris [tm] Operating System, refer to the following URL:
http://www.sun.com/software/solaris/mozilla/

6. Documentation

You can find them at the following locations:

Mozilla 1.2.1 for Solaris [tm] Operating System Release Notes:
(http://docs.sun.com/db/doc/817-2603-10)

Frequently Asked Questions (FAQ) for Mozilla 1.2.1  for Solaris [tm] Operating System Release Notes::
(http://wwws.sun.com/software/solaris/mozilla/faq.html)

New manual page:
A new manual for Mozilla 1.2.1 for Solaris [tm] Operating System is provided in your setup directory. Please use the command

man -M $(setupdirectory) mozilla

to see the detailed information about the command "mozilla".

7. Patch List

It is suggested that you apply the following patches to your system for Java 2 SDK, Standard Edition,v1.4.2:
(See: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE)

These patches can be obtained from the same page as the Mozilla 1.2.1 for Solaris download.