In discussions with   xxxxx@xxxxx  , it is clear that the initial JavaScript -> Java call against an applet is being allowed to go through too early. The implicit semantics, which are long-standing, are that the first JS -> Java call is only allowed to be executed once the applet has completed its init() method, unless the applet first makes a Java -> JS call. The fact that fireAppletLoaded() in the Plugin2Manager releases the LiveConnect message queue on the browser side before init() is called is introducing regressions in test cases. This needs to be corrected urgently. It is very likely related to the recent email thread around calls to isActive() causing errors in the IE JavaScript engine.
Posted Date : 2008-05-22 18:48:49.0

Please contact   xxxxx@xxxxx   for test cases that do JS -> Java calls and which do not behave correctly without a workaround (calling Applet.isActive()) to prevent the JS -> Java call from going through too early.
Posted Date : 2008-05-22 19:17:54.0

N/A

fireAppletLoaded is issued before the applet init lock 
was aquired.
Posted Date : 2008-05-23 02:21:39.0

This regression was introduce with CR 6691927,
where I have moved fireAppletLoaded above the init lock
to allow browser messages to come through earlier.
Posted Date : 2008-05-23 05:48:53.0