Talk:Firefox:Download Manager:Scratch Pad

It would be great if the bittorrent protocol was supported for Firefox 2.0. See bug # 236755. Maybe supported in the unified download backend and unified invocation api.

Usecases for user initiated "pause" of a download?

Is pausing a really such a common action for the user that it needs to be the only button on a download? What are the usecases where the user actively pauses a download?

I personally feel that a download should be paused (and resumed) automatically when:

• the overall network connection fails (including dial-up is disconnected),
• the download server connection fails (including too many users on ftp or the torrent tracker is unavailable),
• the browser crashes (only pause when no data corruption on the download has occured) or
• the browser is closed (the current "do you wish to cancel your downloads"-dialog could be replaced by "Do you wish to pause your active downloads and resume then on restart or do you wish to cancel all of them?")

Some of the usecases I could think of include:

• the user needs more bandwith (for streaming video or browsing) - this should be solved by QoS
• a newer download is started which the user want badly - does this occur that often that we need more than a pause option?

Concerning the accidental cancel clicks, it might be solved by pausing the downloads on cancel and only doing the actual deletion on clicking remove or closing the browser.