Applet removing itself from the DOM document tree causes crash




15 years ago
14 years ago


(Reporter: dtrom, Unassigned)




Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031020 Debian/1.5-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031020 Debian/1.5-1

If a java applet removes the corresponding applet element node from the DOM
tree, Mozilla crashes.  This happens reliably.  I'm not sure if it's valid
behavior for an applet to do this, but there should be some way for it to clean
up gracefully.

Reproducible: Always

Steps to Reproduce:
1.  Put an applet in an HTML page in a TD with some ID=xxx
2.  Have the java applet evaluate javascript to get the TD by ID
3.  Have the java applet remove it's own node from the TD.
Actual Results:  

Expected Results:  
I'm not sure how DOM implementation works, but if there is any way to associate
the applet with the page and continue it running, that would be the ideal.  At
very least it should stop the applet gracefully.
This needs a testcase.  I suspect the problem is that the applet itself crashes,
not that the browser crashes....
Keywords: qawanted

Comment 2

15 years ago
David could you set up a testcase with a java applet that simply removes itself?
This would help us greatly to fix this bug. Thanks a lot!
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.