-
Enhancement
-
Resolution: Fixed
-
P3
-
6u10, 6u15, 6u18
-
b05
-
generic, x86
-
generic, windows_vista
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2198810 | 7 | Andy Herrick | P3 | Resolved | Fixed | b104 |
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.
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.
- backported by
-
JDK-2198810 update deployJava.js for chrome and beter version detection
- Resolved
- duplicates
-
JDK-6864400 Unable to load applet someting in google chrome browser, using 6u15-b03
- Closed
-
JDK-6824755 deployJava.versionCheck() fails to detect java when Opera browser is used
- Closed
- relates to
-
JDK-6901706 deployJava.js regression on Firefox when no java is installed.
- Closed
-
JDK-6957129 Java detection doesn't work on Windows Safari
- Closed