JDK-5096710 : PIT:Regression testcasejavax\swing\InputVerifier\4774166\bug4774166.java failing
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_redhat_3.0
  • CPU: x86
  • Submitted: 2004-09-03
  • Updated: 2006-06-28
  • Resolved: 2006-06-28
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.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-6385277 - testcase 4774166 is failing on Linux but passing on Solaris and Windows with Tiger JDKS.
Duplicate :  
JDK-5104873 - RegTest: jjavax/swing/InputVerifier/4774166/bug4774166.java fails on LinuxAs
Description
Regression testcasejavax\swing\InputVerifier\4774166\bug4774166.java failing on Linux As 3.0.

The Java version is : 
java version "swing-jcg-sparc-01-2004-08-23-int.mustang"
Java(TM) 2 Runtime Environment, Standard Edition (build swing-jcg-win-01-2004-08-23-int.mustang)
Java HotSpot(TM) Client VM (build 1.5.0-rc-b63, mixed mode)

Note: THIS BUG IS FILED AGAINST TIGER-RC AS THERE WAS NO ENTRY FOR MUSTANG
Comments
EVALUATION This is a duplicate of 6385277 resolved in mustang.
28-06-2006
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
28-09-2004
EVALUATION Note: The test case in question has yet to be checked back into the workspace. This will happen with Swing's next integration. Note, the test case in question may need other resources from test/javax/swing/regtesthelpers. My investigation into this detects an AWT problem, not reproducible on Windows. On the Windows platform, when the test clicks onto the JTextField in the JWindow, focus moves to that window. On Redhat, focus does not move. Also, this isn't a function of the test being automated. To see this: Comment out the robot code in the test case and launch the application. In the JFrame in the center, click on the top text field to give it focus. Now, click on the first text field in the JWindow. Notice that focus isn't transferred. ###@###.### 2004-09-09 Name: at153223 Date: 09/24/2004 The point is that focus shouldn't be transfered as the top text field has an InputVerifier set on it that doesn't allow to change focus (verify() method returns false anyway). Thus the behaviour described as erroneous is correct! It works correctly (focus isn't transfered) on XToolkit. On the other hand the bug is that focus is tranfered on other platforms (Windows, Motif). On XAWT I see that after I click to a JWindow's component requestFocus() is immediately called on it. On Motif and Windows WINDOW_LOST_FOCUS first comes on the frame and only then requestFocus() gets called. I'm trying to figure out the cause of such a different behaviour. ###@###.### ====================================================================== Name: at153223 Date: 09/27/2004 On XAWT 'Window' is override_redirect (in contrast to Motif and Windows). WM doesn't set focus on it, it's our responsibility. XAWT does nothing with focuses on MOUSE_PRESS in a lightweight component in a JWindow. So only JComponent.requestFocus() affects on focus change. When it asks InputVerifier to permit focus transfer the focus related data are not changed, but ARE CHANGED in case of not override_redirect 'Window' when focus transfer is originally initiated by WM. We should think it over and try to resolve in mustang. ###@###.### 09/27/2004 ======================================================================
27-09-2004