After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600168 - Cannot shift-tab into the rows of a list-view.
Cannot shift-tab into the rows of a list-view.
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-10-30 20:55 UTC by Jud Craft
Modified: 2018-02-10 04:39 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Jud Craft 2009-10-30 20:55:10 UTC
This concerns keyboard navigation into the rows of a list-view (such as the details view in Nautilus, or the library in Rhythmbox).

You can tab-into it and tab-out, but you can't shift-tab back into it.


Reproduction:

1.  [example] Open Rhythmbox.
2.  Press tab to cycle through UI elements, until you reach the list view with columns.
3.  Tab once into the list columns.
4.  Tab once into the list view rows.
5.  Press tab again to move focus to the next UI element (away from the list view).
6.  Try to shift-tab back to the list view.


Observation:
Shift-tab does not return focus to the list view.  It instead jumps all the way back to the list columns.


Expectation:
Since tabbing forward goes in the order:

List Columns -> List Rows -> Other UI

then tabbing backwards should go Other UI -> List Rows -> List Columns.


The list view is included in the forward tabbing order.
It should be included in the backward tabbing order.

Currently you can never enter the rows of a list view using shift-tab, though it works fine with tab.  This is inconsistent.
Comment 1 Matthias Clasen 2018-02-10 04:39:15 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.