Yes. PDFs, docs, images. But also zips put on a FTP by my friends, installation programs, etc.
Let me describe a use-case: 1) One of my friends gives me a link to a zip located on a FTP containing 10 pictures of his last holidays. 2) I download the zip. 3) I open the zip from the download shelf. 4) I drag&drop the files contained in the zip to my pictures folder. Without this feature: 5) I open the folder where the file is located. 6) I manually remove the file. 7) I close the explorer. 8) I remove the entry from chrome://downloads/ since I am not interested anymore in keeping the link. With this feature: 5) I select the "Remove file from hard drive" in the list. 6) I select "Yes" in the dialog that opens up. The size of the downloaded files shouldn't by their own void the need of this feature. On Jul 31, 6:27 pm, Nico Weber <[email protected]> wrote: > Out of interest: This sounds like you often download a file to look at > it once (i.e. what the "Open/Download?" dialog in IE is for). What > filetypes are you doing this with primarily? PDFs, .docs, images, > other? > > > > On Fri, Jul 31, 2009 at 9:19 AM, Emmanuel<[email protected]> wrote: > > > Following Issue 60 (http://code.google.com/p/chromium/issues/detail? > > id=60), I would like to request a feature with the following specs. > > > The feature would allow removing a file that has just been downloaded > > by Google Chrome from the file system. This would work *only for > > downloaded files* located at a place *known by Chrome*; i.e. which has > > been explicitly given to the browser either from within a file > > selection dialog or the "Downloads" option in the options. > > > This feature would be available if: > > - the file is still on the file system, > > - the file is still in chrome://downloads/, > > - the date of the file matches the date at which the file was > > downloaded. > > > The check on the date would prevent the user from removing a file that > > was previously downloaded by Chrome and replaced by a new one > > afterwards. This does not happen often already, but the check on the > > date would even reduce any bad side effect of this feature. > > > This feature would be accessible by: > > - the options available in the download shelf, > > - right-clicking on a download in chrome://downloads/. > > > Clicking the option would: > > - display a "Yes/No" confirmation window that would cancel the > > operation if the user clicks "No", > > - remove the file from the file system, > > - place the file in the trash if the system/desktop/... supports it, > > - remove the entry in chrome://downloads/ if the file has been > > successfully removed. > > > In order to satisfy all users, this feature could be activated by an > > option in the configuration of Chrome. I am not sure whether this > > should be activable or not, but I think it may be a possibility. > > > This feature request comes from: > > - the hassle of passing the whole day opening the downloads folder, > > removing downloaded files and then removing their entries from > > chrome://downloads/, > > - the fact that offering this option would reduce the number of > > "trash" files in the downloads folder, I mean files that you have > > downloaded, installed/viewed and forgot to remove, > > - the fact that it is an innovation; no other browser does actually > > offer such an option, > > - the fact that this feature isn't as dangerous as you may think. > > > More details on the last point: if the user downloads a file in the > > system folder (for example), he/she would remove an important file > > only if he/she has already replaced one. Using the trash if it is > > available would also offer the possibility to restore an important > > file that has been deleted (even if it was already replaced > > previously). I think files should however be deleted immediately if > > the user chose not to use the trash. > > > Thanks for reading. --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
