Closed
Bug 522209
Opened 15 years ago
Closed 13 years ago
File Download not working as expected when target directory is missing.
Categories
(Firefox :: File Handling, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 429827
People
(Reporter: casualprogrammer, Unassigned)
Details
(Whiteboard: [testday-20110715])
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3
Already reported in Novells Bugzilla
https://bugzilla.novell.com/show_bug.cgi?id=385142
When a file is clicked, the download menu opens and lets one select "open" or "download". If "download" is chosen, usually the download starts, displaying the progress.
If a directory is set in "Edit/Preferences/Save files to" that doesn't exist, Firefox will create it, if it is on an accessible media. If the media is not accessible (Removable external drive) the dialog just dies away without further notice, leaving the casual user with the impression all is fine.
Instead the situation should be communicated via a message box, giving user the opportunity to remedy the situation.
Reproducible: Always
Steps to Reproduce:
1. Set download directory to external drive
2. Remove drive
3. Click a download link
Actual Results:
Nothing
Expected Results:
Message informing about the problem, giving opportunity to fix.
Reporter | ||
Updated•15 years ago
|
Component: General → File Handling
Version: unspecified → 3.5 Branch
Updated•15 years ago
|
QA Contact: general → file.handling
Related:
Bug 510791 - Save Dialog doesn't appear when browser.download.dir is a top-level drive that doesn't exist
Bug 440072 - browser.download.lastDir set to unavailable network drive hangs
Bug 458466 - FireFox hangs when downloading a file if Windows User TMP var points to 2nd hard drive
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
Whiteboard: [testday-20110715]
You need to log in
before you can comment on or make changes to this bug.
Description
•