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 781766 - save file dialog needs work
save file dialog needs work
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-04-26 12:52 UTC by Chuck Pergiel
Modified: 2018-04-15 00:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Chuck Pergiel 2017-04-26 12:52:18 UTC
I noticed these problems is xed version 1.2.2, but I think my browser (Chrome) and most other programs use the same save-file-dialog.

The file name is highlighted even when it is not active. Do something like change directory and it stays highlighted. Press control-V to paste a new name and nothing happens. Press the tab key until you get to the file name box and now control-V works. But now press Enter to save the file and nothing happens, which might be okay, but pressing the tab key does nothing either, so you cannot get to the Save button without using the mouse.

The worst part is highlighting the item when it is not active.

Linux Mint 10.1 Serena
Comment 1 Daniel Boles 2017-08-06 01:52:15 UTC
(In reply to Chuck Pergiel from comment #0)
> But now press Enter to save the file and
> nothing happens, which might be okay, but pressing the tab key does nothing
> either, so you cannot get to the Save button without using the mouse.

I can't reproduce this. Tab works - first to the search icon, then the Save button.


For the rest, https://bugzilla.gnome.org/show_bug.cgi?id=785838 is a duplicate, though maybe we should 'split' them and keep that about the selection and this about the apparent lack of tab-ability from the name entry.


If you still have this issue, please confirm your exact GTK+ version and preferably submit a self-contained test case as a C, Python, or .ui file that exhibits that problem.
Comment 2 Matthias Clasen 2018-04-15 00:31:52 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