搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 3 个回答
  • 3 人有此问题
  • 1 次查看
  • 最后回复者为 OBloodyHell

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.

所有回复 (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.