View Issue Details
|Chrono Download Manager
|0001667: Download icon renders as HTML
|The animation overlay which indicates Chrono displays at the mouse pointer location after a file is saved is rendered as an html overlay which can be right clicked and interacted with.
|Steps To Reproduce
|Save a URL, image, or file using the context menu, confirm the dialog box, right click on the download arrow animation icon that pops up, and you can interact with it. Copying image address reveals the following address: chrome-extension://mciiogijehkdemklbdcbfkefimifhecn/icons/newd.png
|I typically save several thousand images a day in my browser. Previously used Firefox because it was the only browser to keep up with all my downloads. Was suggested to use Chrono when I made the switch to Chrome. As such, I develop a sweet-spot in my mouse heat-map and click the same location to download images rapidly. However, due to this bug, I have thousands and thousands of "newd(#).png" files in my folder because I have been clicking the same spot rapidly to save different images as I scroll through them. Because Chrono only confirms with an animation that the file has begun downloading and (by default I guess?) does not have a visual confirmation the file was successfully downloaded, I assumed the files I were trying to save were the ones I was clicking on. This is not the case. Also because Chrono only keeps track of downloads from the standard ht/ftp(s) protocols and not the chrome-extension protocol, I have no history of exactly how may miss-click downloads there were. I can not say on one page of 60 images which ones were not saved because I can not see in order (I usually download from the top of the page down) how many of the items were miss-clicks. I would have to design a program that scrapes every page I visited and compares it to chrono's history and create a list of possible images not downloaded, which could result in millions of unecessarily saved images to sort through. Nothing will bring back the lost data, as some of these were time sensitive images, however I hope if an alternative method of rendering onto the screen through Chrome is found to prevent such misshaps for anyone else in the future.
|No tags attached.
|As of this posting, Chrome Version 60.0.3112.113 (Official Build) (64-bit) still has this bug.
|Had another batch of time sensitive images download as "newd(#).png again. I will have to disable Chrono until the issue is fixed.
|File Added: newd.png
|Note Added: 0000406
|Note Added: 0000407
|0.10.1 => 0.x.0