This appears to be caused by ImageWindow#getMaximumBounds' usage, as it is passed to Frame#setMaximizedBounds. The Rectangle returned specifies a window location on the primary screen, causing the maximized bounds to require window presence on that screen.
Tested on 1.53k.
This appears to be caused by
ImageWindow#getMaximumBounds
' usage, as it is passed toFrame#setMaximizedBounds
. TheRectangle
returned specifies a window location on the primary screen, causing the maximized bounds to require window presence on that screen.