User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b1) Gecko/2007110903 Firefox/3.0b1 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b1) Gecko/2007110903 Firefox/3.0b1 If a script block retrieves a reference to an applet via document.getElementById immediately after the applet has been loaded, the newly loaded applet is stopped and destroyed and a new applet is created. Note that this behaviour occurs not only when the applet is loaded as part of a normal page load, as per the attached test case. It also occurs when the applet is loaded on demand, for example, by setting the innerHTML of a container to the applet tag in response to a user action. Reproducible: Always Steps to Reproduce: 1. Extract the attached jar by running jar xvf appletreload.jar 2. Modify the archive attribute of line 17 of diagnostic.html appropriately 3. Open diagnostic.html in Firefox (bug reproduced in 3.0b1 and 2.0.0.11, not in 2.0.0.7) 4. To view the correct behaviour - that the applet is not destroyed - simply comment out line 21. Actual Results: An applet is created and detroyed, then a new applet is created. Expected Results: Only a single applet should be created. Invoking retrieveAppletRef manually (by clicking retrieveAppletRef) invokes the same function as that which causes the bug, but it doesn't cause the applet to be destroyed and reloaded. That suggests to me that a race condition is highlighted by invoking document.getElementById, that perhaps sends a spurious APPLET_DESTROY method. I reproduced this bug in 3.0b1 and 2.0.0.11 but not 2.0.0.7.

End of description meant to state APPLET_DESTROY event, not method.

Is this a consequence of bug 90268, somehow?

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a4) Gecko/20100407 MozillaDeveloperPreview/3.7a4 Please update if you are able to still reproduce with the latest nightly build ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/

Closing since now after whiteboard closeme date and no reply to last comment. Please reopen/comment with further info, if you still see this issue with Firefox 3.6.13 or later, with a clean profile and the latest version of the plugin. If you wish, you can also try to reproduce in Firefox 4 Beta 8 or later: http://www.mozilla.com/en-US/firefox/all-beta.html