GNOME Bugzilla – Bug 671273
Make Ctrl+Tab move focus between tabs
Last modified: 2018-04-15 00:25:15 UTC
When interacting with a dialog box in GNOME, pressing Ctrl+Tab should advance the focus to the next tab in the dialog box's tab-list. For example, "System Settings > Sounds" contains four tabs: 1. Output 2. Input 3. Sound Effects 4. Applications pressing CTRL+TAB should move the focus among these four tabs. pressing TAB by itself should move the focus to individual elements within each of the tabs. Looking just at System Settings, CTRL+TAB is not working in any of the following dialog boxes: --Background/Appearance --Language Support --Keyboard --Sound --Privacy --Time & Date --Universal Access
Where does it say that Ctrl+Tab is supposed to do that?
I'm requesting an enhancement to make it easier to navigate through Gnome settings.
I would think this should be a GTK+-wide thing. Trying to implement it per-application would be frought with problems.
I think this was his intention, to make it GTK+-wide.
(In reply to comment #4) > I think this was his intention, to make it GTK+-wide. Why filed against the system settings then?
We already have keybindings for moving between tabs: Ctrl-PgUp/PgDown, and if the focus is on the tab label, Left/Right
@ Bastien Nocera It was ignorance on my part for not filing this correctly (GTK+). Sorry for any trouble I may have caused you guys from this mistake. @Matthias Clasen Part of the problem is that Windows users don't know about Ctrl+Page Up. Windows only uses Ctrl+Tab. And since everything else in the windows world also does (eg., Firefox, Chrome, Opera, all Windows programs, etc), users never learn that Ctrl+Page Up exists. I just saw a bug report somewhere else for a Linux application where the user was requesting a Ctrl+Tab shortcut and the developer told them about Ctrl+Page Up and the user had no idea this shortcut existed because he was a Windows veteran and thought Ctrl+Tab was the universal shortcut for moving between tabs. Windows users will assume Ctrl+Tab will move them between tabs. And when it doesn't they will assume no shortcut exists to do this (they will not consider that another keyboard shortcut exists to do the same thing). I wanted to bring this point up so that developers can consider whether Ctrl+Tab support should exist in addition to Ctrl+PageUp. Ctrl+PageUp may be a better shortcut (Windows often does things screwy and shouldn't always be copied). But Ctrl+Tab has wide-spread support across 3rd party Windows applications as well so I thought it should at least be considered. Ultimately you guys may decide that Ctrl+PageUp is enough. But I thought it would be a good idea to at least cnsider Ctrl+Tab support.
*** Bug 671504 has been marked as a duplicate of this bug. ***
Bug 498974 asks for the same thing as this bug, from guidelines point of view. Bug 675592 asks for this to be a platform specific key binding for MS Windows. There is a long list reports against various applications requesting the same thing, such as bug 671507 and the others linked from there. Relevant mailing list discussions: https://mail.gnome.org/archives/usability/2006-March/msg00014.html https://mail.gnome.org/archives/desktop-devel-list/2009-November/msg00220.html
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new