JDK-4980119 : setting maximized bounds to a frame does not work on Solaris - GNOME
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2004-01-19
  • Updated: 2010-12-29
Related Reports
Relates :  
JDK-6464482 - XAWT: Multiple problems setting WM_NORMAL_HINTS
Relates :  
JDK-6234296 - Setting maximized bounds and maximizing the frame moves the frame to a diff loc, XToolkit
Relates :  
JDK-6200438 - Frame's size must be validated against maximized bounds when resizing, win32
Description
I am setting the maximized bounds for a frame to 0,0, 300, 300 and maximizing the frame by calling setExtendedState(). When I execute this application on Solaris9 with GNOME, the maximized bounds.width, height are not honored and the frame gets maximized to the full size of the screen. When I execute on CDE, maximizing operation is not supported. On Win32, this works fine. 
I also tried this on RH9 with GNOME and this seems to be working fine. On RH8 with GNOME, maximized state is not supported.

I have attached a sample testcase. Execute the sample test on Solaris 9 with GNOME session. If the frame gets maximized to the size of the screen, then the bug is reproduced.

This is reproducible right from JDK1.4+.
Comments
EVALUATION To implement setting max size on XAWT XSetWMNormalHints/ PMaxSize is used. And it works fine on some WM (e.g. xfwm, wmaker). Unexpected behaviour on kwin / metacity is WM issue. I have checked that the same things can be noticed with simple native application (attached). Please, look at the following links for more information: http://bugs.kde.org/show_bug.cgi?id=120353 http://bugzilla.gnome.org/show_bug.cgi?id=327543 Using XSetZoomHints doesn't help to fix problem (during the test the state of the window is NormalState). Note about Windows: looks like max size is ignored in case of resize (look at 6200438).
20-01-2006
EVALUATION Since reengeneering is required for setting window size hints should fix this bug together this other (6234296 fox example).
28-07-2005
EVALUATION Name: ynR10250 Date: 01/20/2004 Quick test shows under Gnome/RH9: (1) Maximized state is always reported as supported. (2) With Motif toolkit, maximal bounds are never honored, almost uniformely for metacity, WindowMaker, sawfish, and enlightement. (3) With XAWT/metacity - everything is OK; in maximized state there's no window borders available to change size. Should it be so? (4) XAWT/wmaker,enlightement - initially maximized window has wrong size; afterwards, everything is OK; borders available. (5) XAWT/sawfish - no Maximize button available at all! ###@###.### ====================================================================== On XAWT/KDE no Maximize button available. On JDS Cinnabar b33 maximal bounds are not honored ###@###.### 2005-07-06 14:45:41 GMT
06-07-2005
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
07-09-2004