The following tests fail on Linux:

- test/closed/java/awt/Focus/ActualFocusedWindowRetaining/ActualFocusedWindowRetaining.java
- test/closed/java/awt/Focus/WrongKeyTypedConsumedTest/WrongKeyTypedConsumedTest.java
- test/closed/java/awt/Focus/NonFocusableWindows/NonfocusableOwnerTest/NonfocusableOwnerTest.java
- test/closed/java/awt/Focus/TestNonFocusableMove/FrameJumpingToMouse.java

The following test fails on all platforms:

- test/closed/java/awt/Focus/TypeAhead/TestFocusFreeze.java
Posted Date : 2007-10-15 10:28:06.0

N/A

1. test/closed/java/awt/Focus/ActualFocusedWindowRetaining/ActualFocusedWindowRetaining.java

Sometimes two quick clicks in one frame's title and then another is treated like a
double click in the latter frame and so causes it to maximize. Additional delays
should be added to the test.

2. test/closed/java/awt/Focus/WrongKeyTypedConsumedTest/WrongKeyTypedConsumedTest.java

Long delay between robot.keyPress() and robot.keyRelease() ends up by generating more than
one KEY_TYPED.

3. test/closed/java/awt/Focus/NonFocusableWindows/NonfocusableOwnerTest/NonfocusableOwnerTest.java

AWT has a bug that consists in that DKFM keeps focus on a component after it has been removed.
This breaks the test.

4. test/closed/java/awt/Focus/TestNonFocusableMove/FrameJumpingToMouse.java

The regtesthelpers utilities should be used.

5. test/closed/java/awt/Focus/TypeAhead/TestFocusFreeze.java

The test contains a pitfall in its synchronization logic. Namely in showing the modal dialog
and pressing SPACE. These events are assumed to occur in a fixed order but this is not the case.
They really could occur in any order in the way it is written in the test.
Posted Date : 2007-10-15 10:28:06.0