JDK-6802868 : JInternalFrame is not maximized when maximized parent frame.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: linux_redhat_5.0
  • CPU: x86
  • Submitted: 2009-02-09
  • Updated: 2011-01-19
  • Resolved: 2009-08-18
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
7 b68Fixed
Related Reports
Relates :  
Relates :  
Description
Bug Info
========
JInternalFrame is not maximized when maximized the parent frame.

For reproducing the issue please run the following regression test with JDK7 b45 on RHEL5 machine.

Testcase : javax/swing/JInternalFrame/4190516/bug4190516.java

Test is working fine till 6ur latest builds and not working with JDK build.

Comments
EVALUATION With this fix I roll back the fix for 6647340 I do it for various reasons and the restoring the protected BasicInternalFrameUI.componentListener field is not the most important the whole previously integrated fix for 6647340 doesn't make much sense to me, because we already have the code that properly moves the internal frame's icon please see BasicInternalFrameUI.Handler.componentResized() this code is just erroneously switched off when the frame gets iconified In the old version of BasicInternalFrameUI, before the fix #6647340 in the lines 1455 - 1461, the componentListener was removed when the frame gets iconified (in this case "ancestor" property if fired) So these are the only lines I didn't restore componentListener is removed in uninstallListeners() and when the frame is closed, but not when the frame is iconified
13-02-2009

EVALUATION This regression started to appear in JDK7 b38; most likely this is a result of the fix for 6647340
09-02-2009