JDK-4900778 : SwingSet2,WindowsL&F:InternalFrameGenerator become maximum when closing maxFrame
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.4.2_01
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-08-04
  • Updated: 2003-10-20
  • Resolved: 2003-09-30
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.
Other
5.0 tigerFixed
Related Reports
Relates :  
JDK-4424247 - DefaultDesktopManager does not handle InternalFrame state changes as expected.
Description
JDK            : JDK1.3.1, JDK142, JDK142_01
Platform[s]    : PC Windows

How to reproduce:
1. Launch demo/jfc/SwingSet2/SwingSet2.jar
2. Change to Windows Style Look&Feel.
3. In InternalFramesDemo, maxiumize any internal frame. Then, close the maximum frame .
After the frame got closed, the InternalFrameGenerator will become maximized.  This behavior is different from other Look&Feel.

###@###.### 2003-08-04
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger VERIFIED IN: tiger-beta
14-06-2004
PUBLIC COMMENTS Verify the fix with JDK1.5 b24 on Windows XP and Windows 2000. ###@###.### 2003-10-20
20-10-2003
EVALUATION This was fixed in 1.5 with the desktop work done for 4424247. ###@###.### 2003-08-11
11-08-2003