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 315523 - Entering a filename in "Open Location" dialog reveals it instead of opening it
Entering a filename in "Open Location" dialog reveals it instead of opening it
Status: RESOLVED DUPLICATE of bug 158423
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.8.x
Other All
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-09-08 11:15 UTC by Christian Neumair
Modified: 2005-11-11 20:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Christian Neumair 2005-09-08 11:15:47 UTC
[1] complains that entering a filename in the "Open Location" dialog of the file
chooser does not open it instantly but instead reveals it in the GtkFileChooser,
forcing you to confirm your choice twice. This seems to be reasonable for
folders, since the user might want to browse deeper in its hierarchy, but for
files it is IMHO obvious that a final choice was requested.

Usability crew, was there any rationale behind this?

[1]
http://www.heise.de/newsticker/foren/go.shtml?read=1&msg_id=8791751&forum_id=84431
Comment 1 Calum Benson 2005-09-20 12:27:43 UTC
I see that the OSX dialog does the same thing, so perhaps the folks who designed
the gtk+ version just drew a little too much inspiration from that :)

There is some justification for it on OSX-- you don't have the helpful filename
completion while you're typing that you get in gtk+, so the selection allows you
to see whether you've actually typed a valid filename at all.  Also, if you set
the OSX dialog to browser rather than list/tree mode, you get the opportunity to
view all of the file's Information (the equivalent of File->Properties in
nautilus) before you open it, which you don't in gtk+.

So, +1 from me on altering the gtk+ behaviour-- it's annoyed me a good few times
too.
Comment 2 Federico Mena Quintero 2005-11-11 20:29:15 UTC

*** This bug has been marked as a duplicate of 158423 ***