EVALUATION
The HTML page attached with bug report results in creating plug-in frame, it gets destroyed immediately, and then the frame is created again. When the frame is created for the second time, we fail to create new plug-in object, instead we use the old plug-in object which is not initialized correctly and this results in NullPointerException. The crash in 1.4.0_0x releases is duplicate of #4599575
I could modify the HTML page to have the applet loaded. However, the second call in the javascript fails because private class's method is accessed. When I make the class public, the applet works fine. The modified HTML and Java files are available in the attached zip file called working.zip
###@###.### 2002-09-2
This requires modification to plug-in shutdown sequence which will be a major change. Hence will commit to tiger. Since this test case is not a common scenario, I will lower the priority to p4.
For the error reported in the coments section, we can file a another bug.
###@###.### 2002-11-12
When any control is loaded through an APPLET tag which is generated dynamically, the control is inplace activated, deactivated and then activated again. This looks to be a Microsoft bug.
The workaround in our code is to reload the control
###@###.### 2003-08-03
|
Java