Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why is THIS: browser.download.manager.quitBehavior;2 NOT the DEFAULT?

more options

browser.download.manager.quitBehavior;2

Why would this behavior -- not closing the browser when downloads are in progress -- NOT BE THE DEFAULT BEHAVIOR?

I lost two very long downloads because I had thought them completed and hadn't specifically checked it. It's hardly the first time, either.

browser.download.manager.quitBehavior;2 Why would this behavior -- not closing the browser when downloads are in progress -- NOT BE THE DEFAULT BEHAVIOR? I lost two very long downloads because I had thought them completed and hadn't specifically checked it. It's hardly the first time, either.

All Replies (3)

more options

Hello OBLoodyHell,

I am sorry to hear that you are experiencing issues with Firefox and that you have lost downloaded files, but you are using an old version of Firefox and there might have been a bug with it. You should reinstall (and not upgrade) Firefox to 12.0 to ensure that everything works correctly.

Thank you for your patience and please let me know how it goes.

more options

The default is to pause a download and resume the download automatically the next time.
That will work in most cases but not in a situation where a link is onyl valid for a limited time or you aren't allowed to resume a download.

more options

The default is to pause a download and resume the download automatically the next time. That will work in most cases but not in a situation where a link is onyl valid for a limited time or you aren't allowed to resume a download."

Which is... most cases. Certainly it's the case for many sources for a very large file. It's just flat out obvious that it should be the default -- if it turns out I want to resume the file download, then ASK if you want that option.

But if you've got a choice between two options, one of which totally screws some people with no warning, and the other which does not, which one do you think most prudent to take? Hmmm?

I shouldn't even have to point this out, it should be obvious to anyone daring to call themselves a programmer:

Choose the path that offers the least opportunity to inadvertently screw over the user.