JDK-6750731 : "javascript:alert(window.java);" fails on FF3 using 6u10-b33
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_vista
  • CPU: x86
  • Submitted: 2008-09-21
  • Updated: 2011-02-16
  • Resolved: 2008-10-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6u10 b33Fixed
Related Reports
Relates :  
JDK-6742245 - Support calling non-Java languages from JavaScript
Relates :  
JDK-6745485 - Firefox browser crash with "javascript:alert(window.java);"
Relates :  
JDK-6688396 - Exception getting thrown on refreshing the applets and JVM fails to start sometimes
Description
The following testcase for 6745485 is failing on 6u10-b33:

http://j2se.east.sun.com/deployment/www/tests/1.6.0_10/6745485/

I tested this on Vista64 FF 3.0.1, using b32 and b33.  There are 2 issues that I noticed:

1) On both b32 and b33, you get the following exception in the java console:

---------------------------------------------
java.lang.Exception: comp is null
   at sun.plugin2.applet.Plugin2Manager.runOnEDT(Unknown Source)
   at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
---------------------------------------------

2) On b33 only if you type "javascript:alert(window.java);" in the address bar, the dialog will not come up. In b32, it does.
Comments
SUGGESTED FIX webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u10/6750731.0 testcase: http://j2se.east.sun.com/deployment/www/tests/1.6.0_10/6750731/
22-09-2008
EVALUATION A "return" statement and test for a nonexistent "toString" method was missed in the refactoring performed in 6742245, which caused the regression in the test case for 6745485. A missed check in the fix for 6688396 was causing the Exception "comp is null" to be printed to the Java Console upon accessing the global Packages, java and netscape keywords in Firefox 3 only. A test case from the forums related to the handling of the Firefox-specific "dummy applet" which implements the Packages, java and netscape keywords showed the need to change the thread which starts the dummy applets to a non-Event Dispatch thread for robustness.
22-09-2008