GNOME Bugzilla – Bug 79319
"File Upload" dialog forgets last selected directory
Last modified: 2004-12-22 21:47:04 UTC
When you click the "Browse..." button beside a file upload field, if that field was empty, then the "File Upload" file browser that appears defaults to the user's home directory, regardless of that last directory you were in when you last selected a file to upload. If the upload field already contains a filename in a specific directory, then the "File Upload" dialog does go to the directory containg that file, but it doesn't go to the last one if the field was blank. The "File Upload" dialog should return to the directory you were browsing when you last chose a file to upload. This is the behaviour in Internet Explorer, Netscape 4.x, and Mozilla. This is very annoying when I have a form that asks for a bunch of files from the same directory to be uploaded at one time, which is very common in such web applications as: - message boards that allow you to upload multiple images in a message (e.g., sfs 1.0 - though that app isn't distributed on the Web yet, but I'm sure there are others); - remote file management apps that support uploading multiple files at a time (such as the one included in CPanel 4, a common tool for administering a website through a browser).
*** This bug has been marked as a duplicate of 6791 ***
No, this is not the same as bug 6791. That bug is about the relationship between the "Selection" textbox and the "Directories" list in the "File Upload" dialog window (and to me appears to be a Gnome or GTK bug, but I could be wrong). This bug is definitely a Galeon bug and has nothing to do with components of the file browsing dialog. It is solely about the directory that this dialog defaults to when it is displayed (which is after you click "Browse..." beside a file upload field in a web page). Please reopen this bug. (I tried but Bugzilla says I'm not allowed to do that.) It's definitely not the same as bug 6791.
Oops, very sorry about this, it was an half-automated reaction :)
There is a patch for this bug in the debian bug #201854 and its against 1.3.5
Has anyone had chance to review the patch?
*** Bug 128140 has been marked as a duplicate of this bug. ***
Fixed in CVS: http://lists.gnome.org/archives/cvs-commits-list/2004-February/msg05423.html