JDK-4303294 : Implement discontinuous selection from the keyboard for list-like components
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.2.2,1.3.0,1.4.0,1.4.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS:
    generic,solaris_2.4,windows_nt,windows_xp generic,solaris_2.4,windows_nt,windows_xp
  • CPU: generic,unknown,x86
  • Submitted: 2000-01-07
  • Updated: 2017-05-16
  • Resolved: 2003-08-15
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.
5.0 tigerFixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Name: lm3724			Date: 01/07/2000

What is the feature and what problem is it solving?:
It is currently not possible to select discontinuous component from a list-like 
component.  This significantly degrades access for disabled users must use a 
keyboard for an input device.

How will it work?:
Implement discontinuous selection in list-like components.  This will probably 
require one or more API changes to Swing components.

What are the benefits over other solutions?:
(not applicable)

###@###.### 11/2/04 16:38 GMT

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b16

EVALUATION Should implement for Merlin. lynn.monsanto@Eng 2000-01-14 Name: db100478 Date: 09/08/2000 Committing to merlin release ====================================================================== As this requires a change to either the DefaultListSelectionModel, or a new ListSelectionModel, I'm reassigning to Swing. ###@###.### 2001-11-28 Just a reminder that we should take a look at 4759422 when fixing this bug, as it also deals with keyboard navigation/selection (in JTable). ###@###.### 2003-06-24 This bug has now been fixed. Here's a summary: JList, JTable, and JTree all now support discontinuous selection through the keyboard. It is available when the component is in discontiguous selection mode (see ListSelectionModel.MULTIPLE_INTERVAL_SELECTION and TreeSelectionModel.DISCONTIGUOUS_TREE_SELECTION). With JTable and JList, the new behavior is only enabled if the underlying selection models are instances of DefaultListSelectionModel. When discontinuous selection is enabled, the keyboard user can manipulate the lead index without changing the selection. New key bindings have been added to the UIs to enable this. These bindings are typically the same as the bindings that move the selection, with the addition of a modifier key. (For example, with JList in the Windows look and feel: UP moves the selection up / CTRL-UP moves just the lead up. END moves the selection to the end of the list / CTRL-END moves just the lead to the end of the list). New key bindings have also been added to add/remove items from the selection (For example, with JList in the Windows look and feel, SPACE, CTRL-SPACE, SHIFT-SPACE, CTRL-SHIFT-SPACE have all been implemented to modify the selection as they would on a native Windows list). As much as possible, the selection behavior of JList, JTable, and JTree has been made consistent. As part of this change, JTable was modified such that it now treats the lead, rather than the anchor, as the focused item. This was necessary to facilitate discontinuous selection and to make JTable consistent with JList and JTree. This problem was reported separately as 4759422 (*** more below ***) but has been folded into this bug. Lastly, as part of this fix, a handful of things have been cleaned up with respect to the selection behavior in the three components. For example, I beleive that selectAll and unselectAll behavior now acts like users would expect. ###@###.### 2003-08-08 *** 4849062, which reports the same issue as 4759422, has also been closed as a duplicate of this bug. *** ###@###.### 2003-08-13