Open Bug 434702 Opened 16 years ago Updated 2 years ago

Save file / rename file annoyance

Categories

(Toolkit :: Downloads API, defect)

x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: oparent, Unassigned)

Details

(Whiteboard: DUPEME)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9) Gecko/2008051206 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9) Gecko/2008051206 Firefox/3.0

Minor annoyance and inconsistency when saving the same file twice. Needs extra action to rename the existing file and save the latest one.

Reproducible: Always

Steps to Reproduce:
1. goto http://www.mozilla.org/
2. Download the Firefox/Thunderbird logo ( http://www.mozilla.org/images/feature-logos1.png)
   by right clicking and then "Save image as..."
3. Save it on your file system
4. Download the same file again.
5. A dialog window prompts "feature-logos1.png already exists. Do you want to overwrite ?"
   Reply no.
6. Search for the downloaded file in the explorer view from the download dialog and rename it to "feature-logos1.old.png"
  The name in the "File name" textfield has not changed, it is still "feature-logos1.png"
7. Click the "Save" button.


Actual Results:  
The dialog window prompts again and reads "feature-logos1.old.png already exists. Do you want to overwrite ?"


Expected Results:  
It should simply save the file as "feature-logos1.png".


Workaround: click the "feature-logos1.old.png", it replaces the file name in the textfield, rename it to "feature-logos1.png" in the textfield.
and click "Save."

Note: the bug is reproducible any kind of file

Anyway, it seems that a listener does capture the file renaming event, update some internal representation (as the final dialog shows), but does not update the "File Name" textfield.

For consistency, it should either udpdate accordingly the "File Name" textfield or use the "File Name" textfield content as the actual file name.
Whiteboard: DUPEME
Product: Firefox → Toolkit
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.