321374 - Freeze on missing/misspelled Java applet

Status: RESOLVED DUPLICATE of bug 321376

(Firefox :: General, defect)

Description

[gekacheka]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

An applet tag of the form

<applet code="MissingApplet"
        width="100" height="100">
</applet>

where the file MissingApplet.class does not exist,
causes Firefox to freeze.

Firefox 1.5 with Java Plug-in 1.5.0_06 displays white box where applet
should appear, then throbber freezes and some operations do not work
(such as closing the tab, or clicking a bookmark to load an new page
in a different tab, or displaying the history sidebar).  Closing
Firefox may make window disappear, but process remains and must be
killed via task manager.


Reproducible: Always

Steps to Reproduce:
1. Open html file with <applet> tag with code attribute that refers to missing class file.


Actual Results:  
Firefox 1.5 with Java Plug-in 1.5.0_06:
displays white box where applet should appear, then
- the throbber freezes
- the mouse is stuck in the 'wait' cursor
- closing the tab with the offending page fails
- clicking a bookmark to load an new page fails, even in a different tab
- displaying the history sidebar fails.
- Closing Firefox may make window disappear, 
  but process remains and must be killed via task manager.
- errors appear in java console 
  (right-click on Java icon in task bar, select "Open Console").

Expected Results:  
Firefox catches error and continues to operate.
- throbber completes throbbing
- mouse returns to normal cursor
- closing the tab with the offending page works
- clicking a bookmark to load a new page works
- displaying the history sidebar works
- Closing/exiting firefox removes the firefox process.
- errors appear in java console 
  (right-click on Java icon in task bar, select "Open Console").

Comment 1

[gekacheka]

Sorry, couldn't get it to switch mistaken component qa

*** This bug has been marked as a duplicate of 321376 ***