This is a tracking bug for issues/bugs that need to be release noted in Mozilla 1.2 Final release. Changes and additions to the Mozilla 1.2 Final Release Notes can be submitted here. **DO NOT put Bugscape (commercial) bugs here.**

Information for deleting COMPREG.DAT should be added to the release notes in regard to Bug #171441 which has about 52 dups so far.

bug 78201: Arabic support on Unix/Linux: Starting with Mozilla 1.2beta support for iso8859-6.8x encoded fonts was added on Unix/Linux (previously arabic display and printing was only supported via iso10646-1 fonts). Printing arabic is supported via the Xprint module. iso8859-6.8-encoded fonts are available from http://www.langbox.com/AraZilla/linux/arafontfull-1.2-4.i386.rpm

Guess this is the right place then... In release notes (1.1 and 1.2b at least), there's are two html anchors called "profiles". One is for "<h2>Profile Location" for which the TOC-listing is missing, the second is for "<h3>Setting Profiles" (second subtitle of "Known Problems") for which there is a TOC-listing which refers to the anchor of <h2>. Furthermore, in the chapter "Profile Location", I think some clarification as to the different Microsoft OSes might be useful. Currently, there are three entries: Windows Windows 2000 Windows 95&98 This leaves open questions as to which Windows is meant in the first entry and as to what happens to win ME, XP, NT etc.

The release note says: > 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. J2SE releases previous to 1.3.0_01 will not work with > Mozilla . Many bugs (bug 139789, bug 135640, bug 142773, ++) have been reported were moz crashes with java 1.3.1, but works with 1.4 (on windows at least). I suggest the realse note be uppdated to something like: 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.

bug 122698 - Opening Mozilla might fail if Mozilla is already running. On some platforms, not including Windows, profile locking prevents Mozilla from launching multiple instances with the same profile. A patch is available to detect this condition and open new windows using the existing process.

bug 122698 is *nix-only. Windows and Mac (AFAIK) have their own way to handle it.

Bug 105656 (Wrong profile directory for win NT/2000) is probably a blocker for this bug.

Under "Known problems" -> "Printing": Printing web pages may not print out all pages due to table pagination problems. (Bug 87374) That line should be removed - the bug hasn't seen any relevant activity since a year ago, and the bug was marked VERIFIED WFM 2002-02-22.

Re comment 4, I'd like to point out bug 180517. Basically, jre 1.3.1_02 no longer works with current trunk builds (and may well not work with 1.2final). So I feel that updating the release notes to link to jre 1.4.1 is somewhat of a priority.

Add: Bug 84128 - For security purposes, a href="file:///..." URLs contained in a page served with HTTP or in a mail message are blocked by default. Currently, when such a link is followed, there is no user-visible error message. To enable these links, set the variable "security.checkloaduri" to false in the user.js file located in profile directory.

If you add that, the last sentence should be "Note that setting this preference to false will allow any web site to hang or crash your system, as well as leaving you open to web sites reading any data they want from your hard drive." Which is what that preference change does.

I would definitely agree with what Boris just said in comment 11.

Please finally add: http://bugzilla.mozilla.org/show_bug.cgi?id=94340

There are many things that should be in the release notes but aren't. I saw somewhere that one reason for this is that noone reads the release notes. However, mention needs to be made of the need to upgrade Macromedia Flash to v6, the need to upgrade nVidia video card drivers, a list of what ports Mozilla/Netscape needs to be open on firewalls, along with several other bugs that have the RELNOTE keyword.

Change: Bug 122445 (ATI graphics adapter image corruption) (Bug number is wrong. Needs to be changed to bug 104992.) Add sentences to relnote: This problem appears when colors are set to 16 bit or 32 bit. Workaround: set colors to 24 bit. Bug 122445 - First sentence begins with, "If a username or password is embedded into a URI in the form of http://username:password@sitename.com. Mozilla will not. . . " Remove period after "sitename.com". In relnote for that begins: "Mozilla does not support Dynamic Fonts," add link to bug 52746.

Re: comment 14: what bug numbers are those?

Andrew, The nVidia problem is referanced in comment 1 of the Mozilla 1.1b Release Notes Tracking Bug (155244). This indicates that the nVidia bug is Bug #128961 The upgrade to Flash v6 is mentioned in Bug #155781 The list of ports that needs to be open on firewalls is partially referanced by Bug #94340

Add: Bug 128961 - Mozilla may crash on a Windows system with an nVidia graphics adapter if the driver is old. To avoid crashes, upgrade the nVidia driver to at 30.82 or later.

Using Andrew's format (thanks to him for the private conversation about how best to get release notes in). This is an update to my comment #1 as this bug now has more than 225 dups. Add: Bug 171441 - If you encounter problems downloading files, then delete COMPREG.DAT and restart Mozilla. If you are using Quick Lauch, you may need to reboot your computer as well. On a Windows system, COMPREG.DAT can be found in c:\Program Files\mozilla.org\Mozilla\components or a path like that depending on where you installed Mozilla.

Nominating bug 169339.

Comment #19: is it relevant to add bug 171441 in the releasenotes now that it has been solved and the installer currently removes compreg.dat anyway?

Yes compreg.dat information is important. Even though the installer deletes it, I at several times, and I'm sure others have experienced download problems after installation, that are resolved by it's removal again.

Comment #21, at risk of being a "Mee to", I do think that Bug #171441 must be in the release notes. Yes, it has been fixed. However, one must remember that this is the second time it has been fixed, so it appears that it is very easy to break the fix. So, rather than be inundated with dups, a simple Release Note comment should be made. If nothing else, this may give some idea if anyone reads the release notes before reporting a bug.

Add: Bug 58339 - Before using any Macromedia Flash web pages, or if you encounter a problem with a page that uses Flash, please upgrade to Flash v6 (http://www.macromedia.com)

all that were deemed worthy have been added.

Can we have the 1.2 release notes mention the whole dhtml thing? and how it is succeeded with the upcoming 1.2.1? I tell my webmaster buddies to check the release notes for info on Mozilla, as many are just starting to support it... Easiest to read and understand what limitations are in what versions. .So when the decide what to include in the "This site is designed for _______________" or anything else. That is what they refer to. Can this be added to the release notes to document the flaw in 1.2? (i know it's minor, but lets keep the documentation accurate for webmasters as well as users).

Well, 1.2 is out (and so is 1.3b). Marking this as fixed.