Description of problem: I was trying to download a clip from a dult website and the dowwnload sequence never started (ETA reads Unknown time remaining and 0 byte at 0 bites/s). I right click on the item and I can't choose Abort/Cancel option in the right click menu for some reason. Clicking the Clear downloads button on the top right corner does not remove it as well. Version-Release number of selected component (if applicable): 68.4.1esr How reproducible: Every now and then. Steps to Reproduce: 1. Open Firefox. 2. Make sure you have Video Downloadhelper installed as a plugin. 2. Go to a random adult website. 3. Open a clip. 4. Click to download that clip using Video Downloadhelper. 5. Open the Firefox File download window. 6. The clip doesn't download.
Starting Firefox without using any addon/plugins removes the oportunity to download the clip. Downloading clips from other websites such as YT or similar works just fine with Video Downloadhelper so my guess is that this is an error with either Firefox itself or the website or both.
We are skating on very thin ice here. > How reproducible: Every now and then > Downloading clips from other websites such as YT or similar works just > fine with Video Downloadhelper To look into this, you would have to give a specific URL for us to try; and the pre-requisites [if any] for accessing the site. I am not volunteering. Some things to try or answer: * If the problem arises, does it do so consistently with that same clip (URL); or does it work sometimes with that same clip? * Does it happen with other similar sites, or just one? * When the problem happens, if you quit Firefox and re-start it, does the stuck download still show, or has it disappeared? * After a stuck download, can you initiate others known to work; or is the clip download mechanism seized up? * What happens with different browsers? Whether or not these points are answered, my instincts suggest dropping this bug.
CC: (none) => lewyssmith
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Resolution: (none) => OLDStatus: NEW => RESOLVED