GNOME Bugzilla – Bug 766696
File save as dialog doesn't switch to keyed in path anymore when pressing enter
Last modified: 2017-09-14 10:49:11 UTC
Created attachment 328242 [details] Screenshot showing Save As dialog not switching to keyed in path I run Unity as my desktop environment at the moment. With a recent update, the file save dialog presented to me by Firefox appears to have changed. I'm pretty sure it's an OS dialog and not a Firefox specific control, but please feel free to bounce this to whichever package is responsible for the File Save As dialog generated by Firefox 46.0 in Ubuntu now. In the past, when the save dialog came up, I was able to enter a path (absolute or relative) in the filename field: * If it was a directory path that existed, the directory contents would be shown inside the window, allowing me to then specify a name * If it was a directory path that didn't exist, it'd take me to the deepest part of the path that did match * If it was a directory that did exist, and a filename that didn't, it'd save as that filename in that folder The last is still true, but the others aren't anymore.. Say I have structure: home .../folder ....../sub2 ....../sub3 ... and I last saved into sub3 and I want to save into sub2, if I remove the filename from the name box, and I type ../sub2 and press enter, it doesn't navigate to the folder anymore.. The auto-complete function seems more reliable now, and it knows the folder exists, but the only way to actually show its contents now would be to click through the tree.. This feels like a functionality downgrade. I should be able to type a pathname into the filename area of the dialog, press enter, and have it take me to that particular folder. gedit DOES do the same thing, and to create a new folder, it has a "+" button. In the screenshot "example.png", you can see that the current folder is "folder1" and I've typed in ../folder2 and pressed enter and it hasn't switched to folder2, rather it's remained in the current folder. This would seem to suggest the fact that it's not unique to Firefox and therefore something to do with underlying library. I apologise if I've not selected the correct component/library, please feel free to shift ticket to the correct component if I've guessed it wrong.
Works fine here, in both gtk 3.20 and 3.21. You'll have to let us know what version of GTK+ is installed on your system. Or, even better, report this issue to the Ubuntu maintainers.
1. Coming from a distro, there are all sorts of version numbers over the place. If you can tell me the way to interrogate things to give me the specific version number of things you're after, I'll be happy to supply it. 2. The Ubuntu maintainers were the first people I reported this to. They said the issue is upstream and to report it to you. You can see the discussion in the linked launchpad issue.
Distro: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily GTK Version: $ apt-cache show libgtk-3-0 | grep ^Version Version: 3.16.7-0ubuntu3 (so 3.16.7) Firefox originally was using GTK2, then moved to GTK3. Issue also seen in other GTK3 using app, gedit.
If this works now but did not in an old version, that would indeed be something for the distro to patch, as upstream does not actively maintain GTK+ 3 < 3.22 (with very rare exceptions for security, etc.)