JDK-7083948 : Applet relaunch could carry out-of-date size information
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-08-26
  • Updated: 2013-09-12
  • Resolved: 2011-09-06
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 Availabitlity Release.

To download the current JDK release, click here.
7u2 b04Fixed 8Fixed
The bug is originally reported at re-opened

When applet is relaunched, we use the size information from the original StartAppletMessage, which is likely to have out-of-date size information, especially on Chrome.

Relaunch should always use the latest size information at the point relaunch is requested.

EVALUATION When client VM doing relaunch, we can update the size parameters as we have being update other parameters as needed. It seems to be more reliable to initiate the size information on the server size with actual plugin size any time we send a start message to client VM. However, that would eliminate the possibility to have client VM adjust the applet size. In theory, latest desired size should be with client VM at the relaunch time.