JDK-6514125 : Window's insets are not updated when changing its state
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: linux
  • CPU: generic
  • Submitted: 2007-01-17
  • Updated: 2018-09-05
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
tbdUnresolved
Related Reports
Relates :  
JDK-6504197 - test/java/awt/Toolkit/ScreenInsetsTest/ScreenInsetsTest.java fails
Description
Operating system: Ubuntu 6.06, 32-bit
Desktop: GNOME
Window manager: metacity 2.14.5

I have attached two sample tests. Both of them show a frame and prints its insets in normal and maximized states. The difference between the tests is that in one of them the frame is first in the normal state and then in the maximized state, and in another the state order is reverse.

In the system described above both of insets are equal to [24, 5, 5, 5] when the frame is first shown in the normal state and to [24, 5, 1, 5] when the frame is first shown in the maximized state. I expect another behavior: insets should be always equal to [24, 5, 5, 5] in the normal state and to [24, 5, 1, 5] in the maximized state, regardless of what state the frame is first shown.

This difference may be also found by running 'xprop |grep _NET_FRAME_EXTENTS' for the frame in different states. The value of this property (which is set by window manager to reflect the frame's insets) is different for distinct window states, but Java insets are equal for all the states.
Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
EVALUATION Currently AWT calculates window insets only once (this process varies for different window managers, but usually includes handling of one or several XConfigureEvents) and then this calculated value is cached, used for every getInsets() call and never updated.
17-01-2007