GNOME Bugzilla – Bug 656849
Ctrl+PageUp/PageDown events always handled by treeview
Last modified: 2018-05-02 15:11:03 UTC
STEPS in 3.1.4: 1. Choose a file in Nautilus 2. Right-click and choose Properties 3. Use Ctrl+PageDown to go to "Open With" tab 4. Use Ctrl+PageUp EXPECTED OUTCOME: Goes back to "Permissions" tab ACTUAL OUTCOME: Focus is in the list of applications, cannot switch tab back
Works fine here. Still an issue?
I can reproduce this on master. Also, it applies to Ctrl+PageDown as well. Using Alt+Ctrl+{PgUp,PgDn} gives the expected result. When entering the "Open With" tab, the application list gets focus. Ctrl+PgUp and Ctrl+PgDn will scroll the list. Unlike clicking on PgUp or PgDn without modifier, Ctrl+PgUp and Ctrl+PgDn scroll the list without changing which item is selected. (It looks as if the Ctrl key is "stolen" by the ability to multi-select while holding CTRL, except I can't select multiple items here.) Tested on Fedora 17, via jhbuild, after updating gtk+ and nautilus.
I can confirm this Problem. on Fedora 17/18
-> gtk+ This is not a Nautilus bug, but a consequence of how GtkNotebook and GtkTreeView work. Both define an action for Ctrl+PageUp/Ctrl+PageDown; when a notebook page is switched, the child of that page will be focused (in that case the application list treeview), and will start receiving key events before the notebook. Not much we can do about this, but probably the GtkTreeView handler should avoid eating the event when it doesn't have any effect on the tree selection, and let it bubble up to the notebook in that case.
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.
Yes still an issue. gtk3-3.22.26-2.fc27.x86_64
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/365.