United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-7083948 : Applet relaunch could carry out-of-date size information

Details
Type:
Bug
Submit Date:
2011-08-26
Status:
Resolved
Updated Date:
2011-09-22
Project Name:
JDK
Resolved Date:
2011-09-06
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
7u2 (b04)

Related Reports
Backport:

Sub Tasks

Description
The bug is originally reported at re-opened
http://javafx-jira.kenai.com/browse/RT-12789

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.

                                    

Comments
SUGGESTED FIX

http://sa.sfbay.sun.com/projects/deployment_data/7-client/7083948.0/

Testcase:
http://sqeweb.us.oracle.com/net/sqenfs-1/export1/comp/jsn/users/stephen/deployment_stuff/sqews_int_liveconnect_dt/deployment/src/javafx/fxfeaturesTest/fxfeaturesTest/html/RelativeDMWithDT_50_50.html
                                     
2011-08-27
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.
                                     
2011-08-27



Hardware and Software, Engineered to Work Together