Crash first Applet Window (grown from first HTML page), after opening second HTML page with other Applet Window.



Core Graveyard
Java APIs for DOM
15 years ago
6 years ago


(Reporter: Alex, Assigned: Ashu Kulkarni)


Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

After opening on the same HTML-frame other HTML page, applet grown from first
HTML page will died.

Reproducible: Always

Steps to Reproduce:
1. Please open a page on, or,
2. Please, choose "German" language (sorry, but english a little bit later),
3. After that, You will got on the left side an Applet (let say MAINAPPLET),
4. Please, choose on the MAINAPPLET "Demonstrationen" Menu,
5. After that, please choose on the MAINAPPLET "Internet-Kamera",
6. After that, on the rigth side HTML-frame you will got other HTML page, from
which will grown first Applet (Cameras Control),
7. After that, please, click on "Leuchtschrift",
8. You will got on the right side HTML-frame other HTML page, from which will
grown second Applet,
Actual Results:  
Applet number First died.

Expected Results:  
All Applets should be live (like in IE5.0 and NN 4.79).

I use JDK 1.4.1_02 from Sun.
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: 12 years ago
Resolution: --- → EXPIRED
Component: Java APIs for DOM → Java APIs for DOM
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.