Annoying "Download save path" behaviour - path jumping between several folders

RESOLVED INCOMPLETE
(NeedInfo from)

Status

()

Firefox
Untriaged
RESOLVED INCOMPLETE
6 years ago
3 years ago

People

(Reporter: jim, Unassigned, NeedInfo)

Tracking

14 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347

Steps to reproduce:

I save many .MP3 files from the same web-page. They all have URL pointing to the same domain in the form "domain.com/get/id-hash", but since it is a huge file storage I do realize that the files may be coming from different web-servers.


Actual results:

Whatever my "Tools -> Options -> General -> Downloads" settings are, "save to" path is annoyingly jumping between several folders I used to save files some time ago.


Expected results:

If I set "Save files to:" in "Tools -> Options -> General -> Downloads", the "Save to" path in the dialog box MUST BE always the one I set.

If I set "Always ask me where to save files", then "Save to" path in the dialog box MUST BE always the last one I saved file to. Ok, there MAY BE different pathes for different extensions, but if I saved file "track1.mp3" into "D:\mp3\" all subsequent savings (track2.mp3, track3.mp3, best_music.mp3 etc.) MUST initially point into this very folder where I saved track1.mp3.
@Reporter: Please confirm this is no longer an issue for you.
If it is, please state your current operating system, Firefox version and detailed test case.

Name 	Firefox
Version 	43.0.4
Build ID 	20160105164030
Mozilla/5.0 (Windows NT 5.1; rv:43.0) Gecko/20100101 Firefox/43.0
Flags: needinfo?(jim)
Closing this as incomplete due to inactivity and lack of response from the reporter. 
Feel free to reopen the bug and provide a test case if the issue still reproduces on a current build.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.