Closed
Bug 85563
Opened 23 years ago
Closed 23 years ago
0.9.2 release notes
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bryner, Assigned: jatin)
Details
Attachments
(1 file)
(deleted),
text/html
|
Details |
This bug is for tracking 0.9.2 release notes changes and additions.
Reporter | ||
Comment 1•23 years ago
|
||
In the mousewheel notes for Windows, remove the following sentence:
Also, mousewheel scrolling will not work if you have the scrolling set to
"full-page mode" in the Control Panel.
Comment 2•23 years ago
|
||
from bug 81652,
------- Additional Comments From Cedric Berger 2001-06-15 13:06 -------
The JAVA section should talk about JDK 1.3.1, which contain OJI for mozilla.
Aditionally, some info related to JDK 1.4beta and Java Webstart (part of
1.4beta) would be useful.
Updated•23 years ago
|
QA Contact: doronr → asa
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
I propose something to be added about bug 74816. For example
Enabling verbose mode:
echo 'user_pref("browser.dom.window.dump.enabled", true);' >>
$HOME/.mozilla/..../prefs.js
Comment 5•23 years ago
|
||
We have still major problems concerning the XSLT support ...
should say something like:
XSLT support still has some major bugs. (Bug 73936, 53030)
Comment 6•23 years ago
|
||
RE: Cedric's comments: I'm not sure what needs to be said about the
newer jdk's. George, could you look over the release notes and see if
anything it out of date.
http://mozilla.org/releases/mozilla0.9.1/
Hey, thanks for copying me on the bug; I *do* have some corrections/additions to
the release notes for the Java portion of the release notes.
* Mozilla 0.9.2 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 0.9.2.
* LiveConnect does work with Mozilla 0.9.2. There remain some LiveConnect
problems with the combination of Mozilla 0.9.2 and JDK/JRE 1.3.X. Fixes for a
number of remaining LiveConnect problems are being incorporated into JDK 1.4 and
will be available when that release of JDK/JRE is available later this year.
* Linux: LiveConnect support now works if you use Mozilla 0.9.2 with JRE 1.3.1.
Additional LiveConnect problems are being incorporated into JDK 1.4 as
mentioned above.
I hope this helps; I don't have any comments about Java Web Start at this time.
Comment 8•23 years ago
|
||
removed bryner's sentence. added george's java verbiage. (to
full-release-notes.shtml)
Comment 9•23 years ago
|
||
everything up to this point has been added (or removed) from
full-release-notes.shtml.
I just checked in http://mozilla.org/releases/mozilla0.9.2/
it should show up on the web site in a while.
Comment 10•23 years ago
|
||
For Bidi and Arabic shaping, I recommend upadting the 0.9.1
wording to the following:
"Bi-directional text support enabled for *Hebrew* and **Arabic** thanks to the
contribution by IBM. Arabic shaping currently works only on Windows platforms
which have full Arabic support installed. (Full Arabic support is available on
Arabic Windows 9x/NT4/2000 and on all language versions of Windows 2000.) On
all other platforms (Linux, Mac), Arabic shaping is not currently available. See
Bug ***82383*** for the status of Arabic shaping code."
The URL links for the asterisked words are as follows:
* --> http://www-5.ibm.com/il/
** --> http://www.wadada.net/alwarda/
*** --> http://bugzilla.mozilla.org/show_bug.cgi?id=82383
Thanks!
Comment 11•23 years ago
|
||
OK, change in wording for Bidi and Arabic shaping
Notes. Replace the above note with the following:
"Bi-directional text support enabled for *Hebrew* and **Arabic** thanks to the
contribution by IBM. Arabic shaping currently works only on Windows platforms
which have full Arabic support installed. (Arabic support is available for Win
2000 by installing an Arabic locale from the install CD. Other Windows platforms
may not provide full Arabic support except under Middle Eastern enabled or
localized versions.) On all other platforms (Linux, Mac), Arabic shaping is not
currently available. See Bug ***82383*** for the status of Arabic shaping code."
The URL links for the asterisked words are as follows:
* --> http://www-5.ibm.com/il/
** --> http://www.wadada.net/alwarda/
*** --> http://bugzilla.mozilla.org/show_bug.cgi?id=82383
Comment 12•23 years ago
|
||
* which still needs to be Mozillafied).
please link to bug 46917
MacOS, OS9 is recommended, bug 87330.
Something along the line of "If you're having problems running other
apps at the same time as Mozilla/N6 you're probably running into a limitation
of Mac OS 8.6 and earlier and you should upgrade to Mac OS 9.1.
I think we have problems w/ the hebrew and arabic language kits on macos. I
should ask the BiDi people.
delete [TEMP]\ns_temp.
should be %TEMP%\ns_temp. If that's inaccurate then the line needs to be
rewritten.
Mac OS: Mozilla installation requires some system extensions like QuickTime.
s/like/including/
Windows and Linux: To run Java applets, you must install the Java Run Time
Environment (JRE) v1.3 plug-in. When using installer builds, everything should
Just Work without any help.
1.3 is inaccurate as 1.3.0_00 will not work...
probably 'Java Run Time Environment (JRE) plug-in v1.3.0_01 or newer.'
There is a 1.3.0_02 for windows, so i'm not sure always talking about 0_01
makes a lot of sense.
With Linux RPM builds, you must install Java as the root user.
s/the root user/a root user/
talk to people at bastille for an explanation of this...
what does:
You may need to press the Stop button for the installation process to complete.
mean? please include a bug number, I never understood this relnote comment.
iirc we don't support Java Plugins on MacOSX in at least some configurations.
bug 81458
Windows, Mac and Linux: Personal Security Manager (PSM) provides security
(cryptographic) features for Mozilla.
We should probably list the other platforms we know that psm does and doesn't
work on. I think Solaris and BeOS are two that it doesn't work on. [don't quote
me]
WinZip references. We should include references to pkware and infozip to be
fair. and perhaps a note that winme has optional zip support.
* Extract the .zip file to a directory such as C:/Program Files/ Mozilla 0.9.2.
tr#/#\\#
'C:\Program Files\Mozilla 0.9.2' would be much better. Encouraging spaces as
leading characters of directory names is rather silly.
these needs a rewrite:
so you may want to do a find in Sherlock for "StuffIt" to make sure that you
don't already have it installed.
i don't understand this:
If you do already have Expander, you need to set it to start by default.
and i'm not quite sure about 'immediately' here:
See the immediately preceding URL for info on using Expander.
it would be much better if we referenced a help/doc url instead...
This seems contradictory, or at least odd:
By default, the download file is downloaded to your desktop compressed in .bin
format. A Mozilla Installer folder is created.
Files Created or Used
this information is way out of date, i've made comments about it a few times
before.
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, edit your prefs.js file as follows:
This can also be done in the debug portion of the preferences dialog in non
release builds, i'm not certain about release builds.
Windows: Double browser window appears when opening an html or image document
from the Windows environment. (Bug 59078)
and bug 88083 and bug 88086 and probably others. -- se: did i miss any?
Message Filters
Multiple filters can apply to a message. ok, that sucked as a relnote. it's
Bug 30081, ask kristif@netscape.com for the ns6 upgrade comment.
Note: Your prefs.js file is located in the Users50 directory on Windows and Mac
OS, and in the .mozilla directory on Linux.
Note: Your prefs.js file is located in the Users50 directory on Windows and Mac
OS, and in the .mozilla directory on Linux.
it must be really important. unfortunately it's wrong. I think the directory is
called Profiles, but that's only some sort of default, plus fuzz.
bug 44071, perhaps bug 77924 and bug 77925
Composer
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.
'set frames' is odd, this relnote should be more prominent (read first
relnote), here is what i wrote when my mozilla-latest-talkback couldn't find
'frames' in the relnotes:
Composer doesn't support frames. It never has, if you want an aol product that
does, aolpress.com has a nice free one. If you try to edit a framed page in
composer, it will open, render, give you an annoying dialog which will close
the document as soon as you click ok. Anyone interested in improving this is
welcome to talk to the Editor people.
I think the preference window is fixed size, so the following needs to be
reconsidered (netscape was going to have a pref to make it variable sized, but
i don't think anyone checked this in onto the mozilla branch):
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)
Preferences might not work if your screen res is 1280xsomethign @90dpi w/ small
fonts. changing to large fonts might 'fix' it (or changing to 640x480, which is
the resolution for which mozilla was 'designed' -- make that 'intended'?)
there's a bug #.
Plugins
Plugins installed for Communicator 4.x may not be available for Mozilla.
Workaround: install these plugins in the Mozilla Plugins folder.
The workaround isn't particularly accurate, some plugins just won't work, we
should list them. At least the popular ones.
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.
should we mention character set auto detect and the view>character coding menu.
s/key// ?
{
POP and Local message body search does not work with non-Latin 1 key words.
Filtering by body key has not been implemented.
}
Comment 13•23 years ago
|
||
What's New In This Release
2nd bullet - prefernce -> preference
6th bullet - to to -> to
Installation Notes - Java
compatability -> compatibility
Comment 14•23 years ago
|
||
Shouldn't this bug get closed?
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•