-
Bug
-
Resolution: Fixed
-
P4
-
1.2.2
-
beta
-
generic
-
solaris_2.5
-
Verified
Click on components in two different windows back and forth. Focus and activation traverses between windows. The event sequence should be in right order as below:
1. focus losing component gets FOCUS_LOST
2. focus losing window gets WINDOW_DEACTIVATED
3. focus gaining window gets WINDOW_ACTIVATED
4. focus gaining component gets FOCUS_GAINED
But the WINDOW_DEACTIVATED is called before the components's FOCUS_LOST in the window which loses focus.
The attached file ClickOppositeWindowsTest2.java reproduces this bug. This test is automated with robot api and should be run in JDK1.2 build which has robot api in it.
This test shows 2 frames and the components in the frames are clicked back and forth..the test fails because of this bug.
Pl. set the path to the framework.jar and lw.jar that are attached to this report to run the test.
1. focus losing component gets FOCUS_LOST
2. focus losing window gets WINDOW_DEACTIVATED
3. focus gaining window gets WINDOW_ACTIVATED
4. focus gaining component gets FOCUS_GAINED
But the WINDOW_DEACTIVATED is called before the components's FOCUS_LOST in the window which loses focus.
The attached file ClickOppositeWindowsTest2.java reproduces this bug. This test is automated with robot api and should be run in JDK1.2 build which has robot api in it.
This test shows 2 frames and the components in the frames are clicked back and forth..the test fails because of this bug.
Pl. set the path to the framework.jar and lw.jar that are attached to this report to run the test.
- relates to
-
JDK-4290675 Focus Management Enhancements
- Closed