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 145167 - file chooser's "open location" considered harmful
file chooser's "open location" considered harmful
Status: RESOLVED DUPLICATE of bug 136541
Product: general
Classification: Other
Component: general
unspecified
Other All
: Normal major
: ---
Assigned To: Unknown User
Unknown User
: 145168 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-06-30 02:27 UTC by Jonathan Koren
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Jonathan Koren 2004-06-30 02:27:34 UTC 
reproduce:
open the new 2.6 file chooser in "open" mode
100% reproduceable

description:
First, pressing CTRL-L is to bring up the "open location" dialog is completely
undiscoverable.  There is nothing in the dialog that indicates that this
capability exists.  This by itself, indicates a break with 20+ years of GUI
development, and leaves users of ALL GUIs confused and frustrated.

Second, user is presented with a dialog in a dialog, which many consider to be
bad form.  What's worse, is that the "open location" dialog only allows
directories to be specified.  Specifing the entire path to the file results in
the main dialog simply changing to the directory the file is located in.  (i.e.
Saying "open location: /etc/passwd" will cause the main open dialog to be set to
"/etc".)

fix:
Eliminate the "open location" dialog, and fold its capabaility back into the
main dialog.
Comment 1 Elijah Newren 2004-07-17 19:07:43 UTC 
*** Bug 145168 has been marked as a duplicate of this bug. ***
Comment 2 Elijah Newren 2004-07-17 19:11:49 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.


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