874324 - double clicking downloading item doesn't pause the download

Status: RESOLVED WONTFIX

(Firefox :: Downloads Panel, enhancement)

Description

[133794m3r]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 (Beta/Release)
Build ID: 20130326150557

Steps to reproduce:

I double click an item that is downloading.


Actual results:

Nothing at all


Expected results:

The item should pause, as was default behavior in firefox ever since v1, and is the default behavior in _every__other_damn_browser_out_there_

Comment 1

[133794m3r]

Additionally because of this issue and forcing me to use an extension to actually be able to use the download manager, I'm going back to 19 or 18, as far back as I have to get the behavior back and not moving until the issue is fixed.

Comment 2

[Maria Grazia Alastra [:mga]]

Hello, did you try clicking on the download button and then clicking with the right mouse button? This should open a context menu containing the option "Pause", at least in Firefox 21.0.
Please let us know if it works!

Comment 3

[133794m3r]

That's not the feature I'm talking about. The pause context menu shouldn't be required to pause a download. By double clicking an item in teh download menu should pause the download w/o having to right click and then use the context menu. Before firefox 20, you could double click to auto-pause it. The context menu is still there. You can't tell me that this feature was a "bug" considering it's been core in the mozilla developers products since my first experience with a web browser(netscape in school). I remember my teacher telling me about how to pause downloads in school. So I don't see how a "bug" in how the system should work could be replicated by all browsers.

So to review, context menu is there, I'm talking about double clicking a downloading item. To review how to see it.

press ctrl+shift+y(still **** on linux it should be ctrl+j nothing is bound to ctrl+j it's dumb to force linux users to press more buttons)
see an item that you're downloading(currently) that's able to be paused. As an example

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/21.0/linux-x86_64/en-US/firefox-21.0.tar.bz2

Download that file, then double click the download labeled firefox-21.0.tar.bz2 it should pause the download. The state should say "paused" in the download manager(the new one btw) it just keeps downloading. The context menu is still there, that's not the issue, the issue is that you can't pause by double clicking the item.

Furthermore, I believe this is an issue with firefox's new download manager. Because if I pause it(either through an extension that takes over the download manager or the context menu) and then double click the paused item, it then starts downloading again. But double clicking it _doesn't_ pause it.

Btw here's the error in the error console(it's ctrl+shift+j so I don't see why ctrl+j still couldn't be used).

Timestamp: 05/22/2013 06:01:10 AM
Error: TypeError: popup is null
Source File: chrome://https-everywhere/content/toolbar_button.js
Line: 45

That is the current time btw, that's the error that is shown

Ok another one that showedup. I still don't know what's going on here, I can't get that one to show up again but this one showed up.

Timestamp: 05/22/2013 06:03:16 AM
Error: NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIDOMJSWindow.setTimeout]
Source File: chrome://downloadmgr/content/browserOverlay.js
Line: 344

Comment 4

[133794m3r]

Attachment: trouble shooting information from the hellp thingy.

this is that stuff, it's the json file, I figure that's what's supposed to be uploaded. If you want I can upload the plain text one instead.

Comment 5

[Simona Badau, Desktop QA]

The patch from Bug 842553 removes the command when double clicking on an in progress download, so this is intended but could still be an enhancement request.

Comment 6

[Marco Bonardo [:mak]]

Pause is an advanced feature, not even supported by all servers.
Many users could be confused by pause on double click, it may also not be great from an accessibility point of view.
I think it's fine to keep it in the context menu, it's still easily reachable.