JDK-6729391 : Draggable signed Applet does not fill screen width when maximized
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-07-24
  • Updated: 2011-02-16
  • Resolved: 2008-07-24
Related Reports
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.6.0_10-rc"
Java(TM) SE Runtime Environment (build 1.6.0_10-rc-b27)
Java HotSpot(TM) Client VM (build 11.0-b14, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
WindowsXP SP2

A DESCRIPTION OF THE PROBLEM :
Signed draggable applets without additional applet close button leave a gap on the right screen side when maximized on windows.

This is not necessary because
1. the warning sign for unsigned applets will not appear anyway
2. the additional close button has not been requested

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Should behave like any other java application
ACTUAL -
Gap for warning sign/close button on right screen side

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
just use the draggable applet example and maximize the applet
optionally enable frame decoration for better debugging:

    public void appletDragStarted() {
// enable default frame docoration and hide applet panel
        Container container = this.getParent();
        while(container != null) {
            if(container instanceof Frame) {
                                
                Frame frame = (Frame)container;
                frame.setTitle("test");
                frame.setResizable(true);
                frame.setUndecorated(false);
                
                frame.addWindowListener(new WindowAdapter() {
                    @Override
                    public void windowClosed(WindowEvent e) {
                        System.out.println("--closing--");
                        if(closeListener != null)
                            closeListener.actionPerformed(null);
                    }
                });
                return;
            }
            container = container.getParent();
        }
}
---------- END SOURCE ----------

Comments
EVALUATION This is intentional per 6702679. The behavior may change in later update releases, but for now I'm closing this as Not a Defect.
24-07-2008