406153 - Download manager always opens original (and oldest) file if there are two of the same name in the list

Status: RESOLVED DUPLICATE of bug 301328

(Toolkit :: Downloads API, defect)

Description

[Ben Thompson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1

There are various bug reports of problems in this area but most are old and none match the behaviour that I can see. It looks like the problems reported in some old bug reports have been fixed but the problem has moved on.

Reproducible: Always

Steps to Reproduce:
Download a file with a given name, e.g. setup.exe, and then another, different file also with the same name. Two setup.exe files will then appear in the download manager. This appears to be what didn't happen in older bug reports.

In C:\Documents and Settings\<username>\Local Settings\Temp there are two files, one called setup.exe and another called setup-1.exe.

However in Download Manager both setup.exe files refer to the file called 'setup.exe' and this can be verified by clicking on the (I) icon which shows the full path to the file stored. This makes it impossible to open the second file without recourse to Windows Explorer.
Actual Results:  
See above.

Expected Results:  
Reference to second file should be to 'setup-1.exe'.

Only happens in Firefox 3.0 beta 1.

Comment 1

[Samuel Sidler (old account; do not CC)]

Dupe of bug 391253 which itself should be WFM? But it was WFM pre-b1, which means it wasn't really WFM?

Comment 2

[Shawn Wilsher :sdwilsh]

Yeah, it's a dupe of that - I don't think it's WFM though...

I think I've seen others of this too.  I know I've seen this issue myself.  Edward I think has a fix in mind...

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

iirc, the problem isn't the on-disk filename (we key that one with (1), (2), etc.), but rather with the Download Manager's UI not being updated to reflect its on-disk filename; it still opens correctly.