Closed Bug 286744 Opened 20 years ago Closed 19 years ago

Crash of FireFox when reloading applet that has the keyboard focus

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: cc, Assigned: bugzilla)

Details

(Keywords: crash)

Attachments

(2 files, 1 obsolete file)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; da-dk) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

First click the button to set the keyboard focus in the Applet. Then reload this page a number of times 
quickly after each other and the press Command-F to see the bug manifest itself.

Reproducible: Always

Steps to Reproduce:
1. Open the "Applet1.html" file
2.First click the button to set the keyboard focus in the Applet. 
3.Then reload this page a number of times quickly after each other and the press Command-F to see 
the bug manifest itself.

Actual Results:  
Crash of FireFox

Expected Results:  
Reloaded the applet and continued without crashing...
Code for applet: 

package ThisIsATest;

import java.awt.*;
import java.awt.event.*;
import java.applet.*;
import javax.swing.*;

public class Applet1 extends javax.swing.JApplet {

// IMPORTANT: Source code between BEGIN/END comment pair will be regenerated
// every time the form is saved. All manual changes will be overwritten.
// BEGIN GENERATED CODE
	// member declarations
	javax.swing.JButton jButton1 = new javax.swing.JButton();
// END GENERATED CODE

	public void initComponents() {
// IMPORTANT: Source code between BEGIN/END comment pair will be regenerated
// every time the form is saved. All manual changes will be overwritten.
// BEGIN GENERATED CODE
		// the following code sets the frame's initial state
		jButton1.setVisible(true);
		jButton1.setSize(new java.awt.Dimension(160, 30));
		jButton1.setText("A button");
		jButton1.setLocation(new java.awt.Point(120, 140));
		setLocation(new java.awt.Point(0, 0));
		getContentPane().setLayout(null);

		getContentPane().add(jButton1);

		setSize(new java.awt.Dimension(400, 300));

		// event handling

// END GENERATED CODE
	}
	

	// Standard method to start the applet
	public void init() {initComponents();}

	// Standard method to start the applet
	public void start() {}

	// Standard method to stop the applet
	public void stop() {}

	// Standard method to destroy the applet
	public void destroy() {}
}
Attachment #177874 - Attachment is obsolete: true
Correct stack trace. Previous was from FireFox 1.0, sorry about the confusion.
(I'm chiming in because I've been CCed on this bug.)

You might want to try the Java Embedding Plugin
(http://javaplugin.sourceforge.net/) to see if it clears up this
problem.

Keywords: crash
Severity: blocker → critical
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: