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 726855 - When subdirectory selected, subdirectory name only briefly appears in location bar and then disappears again
When subdirectory selected, subdirectory name only briefly appears in locatio...
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.11.x
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2014-03-22 00:48 UTC by Adam Williamson
Modified: 2014-03-22 02:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
video illustrating the problem (233.03 KB, application/octet-stream)
2014-03-22 00:50 UTC, Adam Williamson
Details

Description Adam Williamson 2014-03-22 00:48:11 UTC
Bit hard to describe, but here's a video.

This affects at least Transmission, probably other apps. Watch the video: I'm choosing the location to which I want to save a torrent. Watch what happens when I select one of the subdirectories of a directory: its name briefly appears in the location bar, then disappears again, and the subdirectory is unselected.

A few GTK+ releases back there was a bug where, if you actually navigated into the directory you wanted to save to and *that* directory had subdirectories, the torrent would be saved into the first of that directory's subdirectories. To work around that bug, I trained myself just to *select* - rather than navigate into - the directory to which I wanted to save my torrents. Now this bug has popped up, I have to go back to doing the exact opposite! My muscle memory is getting very confused.
Comment 1 Adam Williamson 2014-03-22 00:50:31 UTC
Created attachment 272609 [details]
video illustrating the problem
Comment 2 Adam Williamson 2014-03-22 02:24:21 UTC
er....got any details on the fix? thanks!