Closed Bug 672817 Opened 14 years ago Closed 14 years ago

site-by-site last downloaded-to directory is not always remembered

Categories

(Toolkit :: Downloads API, defect)

7 Branch
All
Other
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla10

People

(Reporter: james, Assigned: darktrojan)

References

Details

Attachments

(1 file, 1 obsolete file)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0a1) Gecko/20110720 Firefox/8.0a1 Build ID: 20110720030844 Steps to reproduce: create a new profile change: options:general:downloads to: 'always ask me where to save files' open http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ click on firefox-8.0a1.en-US.linux-i686.complete.mar file click save file create a new folder on your desktop 'moz' click save open http://winscp.net/eng/download.php in another tab click installation package when the 'opening' dialogue appears click save file create another folder on your desktop 'winscp' click save go back to the ftp.mozilla.org tab click on firefox-8.0a1.en-US.linux-x86_64.complete.mar click save file Actual results: the pre-selected folder for the download is 'winscp' Expected results: folder should be last used folder for ftp.mozilla.org - 'moz' note that if you use right click and 'save link as' on the download links on each tab the last downloaded-to folder is remember per site as expected
Confirm both of your observations. BTW: Since when does Fx recall the directory on a per-site basis? I want the old behavior back: There is a single, current, persistent and changeable download directory for all downloads. Is this configurable?
Blocks: 536503
It is since Firefox 7 and implemented in bug 536503.
Status: UNCONFIRMED → NEW
Component: General → Download Manager
Ever confirmed: true
Product: Firefox → Toolkit
QA Contact: general → download.manager
Attached patch patch (obsolete) — Splinter Review
When saving a file through the unknown content-type dialog, the current code can't find a URI to save the directory for.
Assignee: nobody → geoff
Status: NEW → ASSIGNED
Attachment #568009 - Flags: review?(gavin.sharp)
Comment on attachment 568009 [details] [diff] [review] patch The aLauncher null check seems unnecessary, are there actually cases when it could be null? It would be nice to understand which cases are covered by the aContext case. Is it even needed at all? When would source be null?
Hmmm. According to MXR, the only point aLauncher is null is during a test. I'll figure out how to fix it.
Version: 8 Branch → 7 Branch
Attached patch patch v2Splinter Review
I wish I'd understood this stuff better when I wrote the original bug. :-/
Attachment #568009 - Attachment is obsolete: true
Attachment #571449 - Flags: review?(gavin.sharp)
Attachment #568009 - Flags: review?(gavin.sharp)
Attachment #571449 - Flags: review?(gavin.sharp) → review+
Target Milestone: --- → mozilla10
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
Flags: in-testsuite+
Stefan (Comment 1): A pref to turn back to the old behavior is being created on bug 702748
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: