JDK-7133019 : REGRESSION:7u4 b07 Applets wont load with Chrome
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7u4
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_vista
  • CPU: x86
  • Submitted: 2012-01-24
  • Updated: 2013-10-30
  • Resolved: 2012-06-22
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 7 JDK 8
7u4Fixed 8 b25Fixed
Related Reports
Relates :  
JDK-7040632 - Plugin2 blocks FireFox when loading applet
Relates :  
JDK-7148295 - REGRESSION: 7u4 Applets wont load with Chrome
Description
J2SE Version (please include all output from java -version flag):

7u4 b06 and b07

FireFox and Chrome both fail on b06
FireFox works fine bug Chrome still fail on b07

Does this problem occur on J2SE 1.5 or 6ux?  Yes / No (pick one)

works fine with 6u30, 7u2 and 7u3


Operating System Configuration Information (be specific):
Win_vista


Hardware Configuration Information (be specific):
both x32 and x64


Bug Description:

Build 6 would not even load the applets in FireFox or Google Chrome.

Build 7 is better. FireFox now loads and authenticates. Google Chrome loads the applet, but clicking the button on our sample page does not invoke the applet after it is done loading as it should. Nothing happens.

Internet explorer works for both builds I tested.

The applet does not respond to the usual JavaScript APIs.

Steps to Reproduce (be specific):

Check 'Comments' field
Check the java console log in Comments field.
Comments
The test link could not be used during recent JDK 8 security tightening (b113). Manifest "permissions" need to be added to jar and resign.
30-10-2013
EVALUATION This is a regression introduced in CR7040632. There is a race condition cause the liveconnect call to fail as the applet is not yet completely started. 7119117 fix is related to this, it suppose to ensure applet is ready for liveconnect calls, however, the race condition of browser thread where the queue is empty but the delegated thread call setWindow is not yet back, which will cause AppletID to be NULL, and the binding from JS to the applet failed.
06-02-2012