On Solaris, executing Frame.bounds() returns x and y values which are those of the Frame itself, and not the window manager's window frame containing the Frame. Since there is no way to determine the window manager's window's contribution to the Frame's location, doing absolute positioning of other frames or windows is impossible.

On Win32, the right thing happens (the returned values are in "global" coordinates), so I believe that on Solaris, the value for the Frame's location should be that of the enclosing window manager's window.

See the enclosed program -- notice how it says the bounds are x=4,y=20 when run on Solaris even when the window is in the upper left corner of the screen, and should report 0,0.