JDK-5106068 : Ctr + Tab is not Working in JTable.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-09-23
  • Updated: 2004-09-23
  • Resolved: 2004-09-23
Related Reports
Relates :  
Description
Bug Description:
----------------
Ctr+Tab is not working in JTable,when focus is in table row and press Ctrl+Tab the focus is not shifted out to next component.
The Bug is reproducible only in mustang not in tiger

JDK-Info:
---------
java version "1.6.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-beta-b04)
Java HotSpot(TM) Client VM (build 1.6.0-beta-b04, mixed mode)

Steps to Reproduce:
-------------------
1. Install jdk1.6.0 b04 in testing Windows System.
2. Launch SwingSet2 demo
3. Click JTable in Toolbar and select any row in JTable,now the focus will be in JTable
4. Click Crt + Tab the focus should shift to next component but its not working in jdk1.6.0 b04.

This effects the functionality in JavaWebstart.


###@###.### 2004-09-23

Comments
EVALUATION Name: sh120115 Date: 09/23/2004 In my (fairly recent) 1.6 workspace, I couldn't reproduce this on NT. Hitting CTRL-TAB took focus out of the JTable. Perhaps something's happened in a recent integration? ###@###.### 2004-09-23 ====================================================================== I can reproduce this on Solaris 9 w/ 1.6b04, but not w/ 1.5. ###@###.### 2004-09-23 I can reproduce this on Win NT 4 with the promoted b04. ###@###.### 2004-09-23 I think what happened is that this bug was caused by the (first) fix for 4887999, which has been integrated into mustang (delta 1.232.1.1). More recently, bug 4887999 has been re-fixed (delta 1.241), backing out the original fix. The bug is not reproducible in the Swing workspace, and will not be reproducible after our next integration. This was a tad tricky to track down, as the JTable.java history has become a bit messy (though I've seen worse :), probably from having parallel workspaces. ###@###.### 2004-09-23
23-09-2004