Closed
Bug 299904
Opened 19 years ago
Closed 19 years ago
Add a relnote about java crashes & java versions
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: timd_huang, Assigned: csthomas)
Details
(Keywords: relnote)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050702 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050702 In the recent past, I posted several bug reports: 1. Mozilla Crash when visit some webpages. 2. Mozilla Crash when "Help/About Plug-Ins" (Bug 299605) Following one of the last comments for issue #2, I changed the Java Plug-In to 0.92. (http://javaplugin.sourceforge.net/) It seems the above problems are solved. So, the cause of these problems may lie on the wrong Java Plug-ins. Reproducible: Always Steps to Reproduce: 1. Quit Mozilla, and Down load the new Java Plug-In 2. Drag two files into the Library/Internet_PlugIn 3. Restart Mozilla Actual Results: Problems are gone. Expected Results: Get the latest Java PlugIns in the Mozilla. This may not be a bug report, but just an accidental finding to share with everybody.
this bug really wasn't remotely necessary, but since it's around, someone really should take the time to make some release notes...
Keywords: relnote
| Assignee | ||
Updated•19 years ago
|
Assignee: general → cst
Flags: blocking-seamonkey1.0a?
OS: MacOS X → All
Hardware: Macintosh → All
Summary: May Not be a Bug Report, but just a finding → Add a relnote about java crashes & java versions
Whiteboard: [cst: do this for 1.0a relnotes]
Comment 2•19 years ago
|
||
blocking+ to remind CTho for relnotes :) Confirm it, as it seems valid...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-seamonkey1.0a? → blocking-seamonkey1.0a+
| Assignee | ||
Updated•19 years ago
|
Whiteboard: [cst: do this for 1.0a relnotes]
| Assignee | ||
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•