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 758929 - GtkEntryCompletion should allow for changing the popdown delay
GtkEntryCompletion should allow for changing the popdown delay
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkEntry
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-12-01 21:41 UTC by Christian Hergert
Modified: 2015-12-05 19:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Hergert 2015-12-01 21:41:15 UTC
Different use-cases of GtkEntryCompletion may need different timeouts for the popdown delay. Most use-cases probably are fine with the current hard-coded 300 milliseconds. However, one use case that is not sufficient for, is autocompletion in Epiphany's URL bar.

The delay in Epiphany's location bar results in activating something different than would be expected because the entry completion has not been displayed (and therefore not activating the first item in the list).

Simply changing this to 100msec seems to make epiphany feel a lot more like FireFox in this regard.

I see two options (should we choose to make this configurable).

1) Add a GtkStyleProperty so this is changeable in CSS
2) Add a regular gproperty for completion-delay

Happy to cook up a patch for either, just tell me which would be preferred.
Comment 1 Matthias Clasen 2015-12-01 22:03:39 UTC
The current timeout is 300ms, actually. This doesn't feel like a style thing to me. We did deprecate (and ignore) a bunch of timeout-related settings in the past. But we can certainly discuss adding a property for this.
Comment 2 Christian Hergert 2015-12-01 22:09:00 UTC
Based on a chat with Benjamin, we might also just consider changing it to 100.

I think the primary problem here, is that you can get 2 different results based on how long you wait before pressing Enter. To solve that, we could also just perform what the delay would have done during activate.