Open Bug 1463704 Opened 8 years ago Updated 3 years ago

Closing 'Library' window cancels all downloads without warning

Categories

(Toolkit :: Downloads API, defect, P3)

defect

Tracking

()

People

(Reporter: matejm98, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20100101 Steps to reproduce: When Library window is closed and a download is still in progress no warning is shown and download is interrupted. Expected results: There should be a warning preventing me from accidentaly cancelling my downloads if 'Library' is the only window open from Firefox
If Firefox exits without warning when you have running downloads, they should be resumable. If the downloads don't resume when next starting Firefox, please provide at least one example download link.
Component: Untriaged → Downloads API
Product: Firefox → Toolkit
You can try this one: https://git-scm.com/download/win After starting Firefox again the download is listed as failed.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 20180523100147 Sorry about the previous comment. The issue is reproducible if the Library window is the last Firefox window to close: 1. Open the Library window ("Show All Bookmarks" / Ctrl+Shift+B). 2. https://git-scm.com/download/win 3. Start downloading a file there, e.g. https://github.com/git-for-windows/git/releases/download/v2.17.0.windows.1/Git-2.17.0-64-bit.exe 4. Close the main Firefox window. 5. Close the Library window. Actual results: Firefox quits with no warning, canceling the download. Expected results: The following warning: Cancel All Downloads? If you exit now, 1 download will be canceled. Are you sure you want to exit? [Cancel 1 Download] [Don't Exit]
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Priority: -- → P3

Almost 2 years after and still no fix?

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.