Bug ID: JDK-6618538 test java/awt/event/HierarchyEvent/AncestorResized/AncestorResized.java fails with JDK 7, 6, and 5

Versions (Unresolved/Resolved/Fixed)

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

The test java/awt/event/HierarchyEvent/AncestorResized/AncestorResized.java fails with the following output:

java.lang.RuntimeException: No ANCESTOR_RESIZED events received.
	at AncestorResized.fail(AncestorResized.java:241)
	at AncestorResized.init(AncestorResized.java:127)
	at AncestorResized.main(AncestorResized.java:167)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:623)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:675)

It seems that it fails even with JDK 6 and 5, not only 7th.

This failure was also observed on Windows 14 GA and 15 EAP 25
02-06-2020
- 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 It's been noticed that the test does not fail on modern Xorg servers (1.6.0) given that the size-grip location fix is applied. However, it fails on 1.4.2. Experiments show that the XWarpPointer() function must be called twice in the AWT Robot peer implementation to make the X server actually resize the window. That is currently unclear whether this might be an issue of the version of the X server, or a specific mouse-related setting. The test needs to be re-verified on a couple of other newer systems. If it passes, then the only thing that needs to be done is decribed in the previous Evaluation entry. Otherwise, investigation should continue.
23-10-2009
EVALUATION It has been noticed that using the approach like this: robot.mouseMove(bounds.x + bounds.width - 1, bounds.y + bounds.height - 1); to move the mouse pointer to the "size-grip" of the window doesn't work properly if the window decorations are slightly rounded. In this case the window doesn't get resized, and the test fails. Using the (-3) value definitely restores the correct behavior of the test, however the test still fails. Note, that, say, the test test/java/awt/Frame/DynamicLayout/DynamicLayout.java uses exactly the same technique, but doesn't fail because it expects no changes, and... gets no changes. But the test AncestorResized.java DOES EEXPECT some changes (some events), and doesn't get any, and hence it fails.
22-02-2008

Relates :	JDK-6533330 - regresssion: ancestorResized event is not triggering, when resizing the frame.
Relates :	JDK-6500477 - 7.0 Regression: setDynamicLayout(false) doesn't work