Closed Bug 273766 Opened 20 years ago Closed 20 years ago

Firefox doesn't always ask where to save a file even though the preference is set

Categories

(Toolkit :: Downloads API, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 257143

People

(Reporter: rtglover, Assigned: bugs)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 When following a link to a binary file, sometimes Firefox asks me where to save the file and sometimes it doesn't, even though the preference to ask for every file is set. Reproducible: Sometimes Steps to Reproduce: 1. Make sure these prefs are on: "Ask me where to save every file" and "Show Download Manager window when a download begins" 2. Visit the sample URL. 3. Left-click on the links for sql2kasp3.exe, sql2kdesksp3.exe, and sql2ksp3.exe 4. If Firefox prompts you for where to save the file, cancel at that dialog or in the download manager and try the next file. Cycle back to the beginning if necessary. I experienced the problem about one-third to one-half of the time. Actual Results: Sometimes the download would simply begin without a file-save dialog to ask where to place the download. Expected Results: With the "Ask me where to save every file" option set, I would expect it to ask every time. browser.download settings: .defaultFolder = empty string .dir = a path to a valid directory to which I have full access .folderList = 0 .lastDir = same value as dir .manager.retention = 0, 1, or 2 (problems occurred with each of these values) .useDownloadDir = false .manager.useWindow = true
Although this is not a precise duplicate of bug 257143, I believe that any fix for that bug will stand a good chance of hitting upon this one as well. *** This bug has been marked as a duplicate of 257143 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.