JDK-8135177 : Inconsistency between location and height of the fullscreen window in Gnome 3, OEL 7.1 in multiscreen mode
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 8,9
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-09-08
  • 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 :  
Description
Compile and run the attached test (2 files and a picture) on OEL 7.1 in multiscreen mode (I'm not sure if it is reproducible on a single screen: the insets bug JDK-8134669 is not).
Eventually it will push a java.awt.Window to fullscreen mode and query its location by getLocationOnScreen.
Now, Window.toString() reports it as [0,0,couple-of-big-numbers] with zeros in parent coordinate system but getLocationOnScreen() reports [0,top-inset-size] ( in my case, [0, 28] ). 
Note also, that getInsets() return all zeros (see JDK-8134669).

Reproducible at least on jdk9 and 8 so that may be some JDK+Gnome 3 issue.
Comments
Retargeted to tbd_major as not a regression in 8u/9 and introduced in 8 GA or earlier. However might be fixed in 9 in positive case on time resources
11-07-2016

No, I don't think it's OEL-specific but it may be Gnome 3-specific. The issue above is someway similar but still different. A main point of difference here is, the multiscreen layout. I just checked it again: the bug was NOT reproducible in a single-screen setup. And from public API point of view, the test code doesn't call getLocation() but only getLocationOnScreen(). Even java.awt.Component doesn't call it for the internal use AFAIK.
09-09-2015

Are sure that it is OEL 7 specific? There is similar issue in Ubuntu: JDK-8011616.
09-09-2015