Closed Bug 471965 Opened 15 years ago Closed 15 years ago

Downloads fail without error/warning when download destination no longer exists

Categories

(Toolkit :: Downloads API, defect)

x86
Windows Server 2003
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 429827

People

(Reporter: mariusads, Unassigned)

Details

(Whiteboard: [DUPEME?])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

Firefox was configured to download to a folder, let's say S:\Downloads.
After a computer upgrade,drive was removed from computer and replaced with a better one, so destination no longer exists, not even the drive letter.

When downloading something, there's no warning or error message, the file does not appear in the Downloads window.
 

Reproducible: Always

Steps to Reproduce:
1. remove a drive or change the drive letter from computer management (if using windows)
2. attempt to download files using "save to disk" option.

Actual Results:  
Nothing. No notification that downloads fail.

Expected Results:  
Should notify files can't be saved to destination and offer to download to My documents or suggest I change the destination.

Similar to bug 409154 but there's talk about aliases and files being saved but not the correct content and so on.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090103 Minefield/3.2a1pre

I can indeed reproduce this. I don't know what they mean by "alias" in bug 409154, but it seems indeed similar. Possibly there are already other duplicates, for this bug sounds very familiar to me.
Component: General → Download Manager
Product: Firefox → Toolkit
QA Contact: general → download.manager
Whiteboard: [DUPEME?]
Version: unspecified → Trunk
I think it should show the filepicker, by the way.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.