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 307802 - Hitting Tab more than once should scroll the completion list
Hitting Tab more than once should scroll the completion list
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkEntry
2.6.x
Other All
: Normal enhancement
: Small fix
Assigned To: Federico Mena Quintero
gtk-bugs
: 327618 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-06-15 16:29 UTC by Federico Mena Quintero
Modified: 2018-04-15 00:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Federico Mena Quintero 2005-06-15 16:29:48 UTC 
In the location entry, hitting Tab inserts the longest common prefix and brings
up the disambiguation list.  After doing that, if you hit Tab again, you get
nothing inserted and get the same list.  Instead, we should scroll the list down
by a page-ful to make it more like Emacs.
Comment 1 Matthias Clasen 2005-06-18 15:20:02 UTC 
Sounds like a good idea.
Comment 2 Federico Mena Quintero 2006-03-06 19:20:33 UTC 
*** Bug 327618 has been marked as a duplicate of this bug. ***
Comment 3 Federico Mena Quintero 2006-03-06 19:21:39 UTC 
The completion box also disappears and appears again when you hit Tab, causing a lot of visual clutter.
Comment 4 Matthias Clasen 2015-07-31 14:29:47 UTC 
The file chooser entry is using entry completion, so would have to be handled there.
Comment 5 Matthias Clasen 2018-02-10 05:24:27 UTC 
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.
Comment 6 Matthias Clasen 2018-04-15 00:32:23 UTC 
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