JDK-6877996 : update deployJava.js for chrome and beter version detection
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10,6u15,6u18
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_vista
  • CPU: generic,x86
  • Submitted: 2009-09-01
  • Updated: 2010-09-16
  • Resolved: 2010-01-08
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 JDK 7
6u18 b05Fixed 7Fixed
Related Reports
Duplicate :  
JDK-6824755 - deployJava.versionCheck() fails to detect java when Opera browser is used
Duplicate :  
JDK-6864400 - Unable to load applet someting in google chrome browser, using 6u15-b03
Relates :  
JDK-6957129 - Java detection doesn't work on Windows Safari
Relates :  
JDK-6901706 - deployJava.js regression on Firefox when no java is installed.
Description
We discovered that chrome and safari require a "code" attribute to run an applet.
In order to provide support on these browsers, deployJava.js should generate a dummy code attribute if one is not supplied by the caller.
any value will do such as code="ignored" but missing this attribute causes the plugin to never be invoked.

Also discovered, Chrome and Firefox could return the exact update version of the latest jre installed even w/o the dt plugins installed.  We should update the detection logic to return the full version from getJREs() when that is possible.
Comments
EVALUATION we can fix this in deployJava.js
01-09-2009