-
Bug
-
Resolution: Duplicate
-
P3
-
9
-
Ubuntu 16.04 Unity, dual-screen
This test fails on Ubuntu 16.04 Unity (incidentally dual-screen) since jdk9 b130.
On b129 we have a maximized frame with a huge button. Robot positions mouse pointer in the middle and clicks, that's it.
On b130/132 there is a small button in top left corner. getLocationonScreen() returns something twice below the height of this small button, and the test fails.
Note that if I comment out the f.pack() in line 79, there's no button at all, since b130. Perhaps the change failingJDK-8164466 and other similar is in pack() behavior.
RULE "java/awt/Mixing/Validating.java" Exception java.lang.RuntimeException: The button cannot be clicked.
On b129 we have a maximized frame with a huge button. Robot positions mouse pointer in the middle and clicks, that's it.
On b130/132 there is a small button in top left corner. getLocationonScreen() returns something twice below the height of this small button, and the test fails.
Note that if I comment out the f.pack() in line 79, there's no button at all, since b130. Perhaps the change failing
RULE "java/awt/Mixing/Validating.java" Exception java.lang.RuntimeException: The button cannot be clicked.
- duplicates
-
JDK-8165619 Frame is not repainted if created in state=MAXIMIZED_BOTH on Unity
-
- Resolved
-