Red Hat Bugzilla – Bug 173293
File name is lost in File-Save dialog when a new folder is created
Last modified: 2008-08-02 19:40:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
In the File-Save dialog, when I create a new folder, the file name disappears from the "Name" box in the dialog. Seems to be gnome-wide; I see it whether saving images in Firefox, or saving documents in OOo, for example.
It happens when I hit enter to complete the naming of the new folder, or if I click into the new name's box. If I click on another flie in the list of files, it works right--that is, the new folder is created, focus is moved into it, and the filename is preserved. But if there are no other files in that folder, then there's no workaround, and anyway it's nice to hit enter to save a folder name.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Right-click on an image on a web page and pick "Save Image As."
2. Click "browse for other folders."
3. Click on the "new folder" button.
4a. Type in a name for the new folder and hit enter, or
4b. Type in a name for the new folder and click almost anywhere except on another filename in the list.
Actual Results: The filename in the "Name" box disappears.
Expected Results: The filename should have remained in the "Name" box.
Oops. Step three should be
3. Click on the "Create folder" button.
This seems to be a duplicate of bug 169899. Firefox and gedit do it, too.
Is there any work ongoing? Hopefully at least FC5 will get a fix for that issue.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
At least solved in FC6
it is also solved in FC5, as far as I can tell. This bug can be closed, I think.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)