> Issue is if one internal frame is open and maximized and another internal > frame is created which is initialized with `setMaximum(true)` then after > opening the second internal frame the new internal frame is opened as > non-maximized > > The fix makes sure the 2nd internal frame remains maximised if it is set with > maximized attrbute, that is > If the current frame is maximized, transfer that attribute to the frame being > activated. > which is also mentioned in this comment > https://github.com/openjdk/jdk/blob/46ee8d550e42f756dd04fa67ed549c93b632df77/src/java.desktop/windows/classes/com/sun/java/swing/plaf/windows/WindowsDesktopManager.java#L70-L71 > > This code seems to be added for > [JDK-5036083](https://bugs.openjdk.org/browse/JDK-5036083) which expects > When a frame is maximized and then minimized, the next frame should NOT be > maximized. > > It still honours that fix as the test mentioned in JDK-5036083 works as > expected as mentioned above along with fixing the present issue..
Prasanta Sadhukhan has updated the pull request incrementally with one additional commit since the last revision: Test fix ------------- Changes: - all: https://git.openjdk.org/jdk/pull/28502/files - new: https://git.openjdk.org/jdk/pull/28502/files/54aa3b61..c6cdaaff Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=28502&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=28502&range=00-01 Stats: 1 line in 1 file changed: 1 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/28502.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/28502/head:pull/28502 PR: https://git.openjdk.org/jdk/pull/28502
