Inability to copy-replace files/folder in ChromeOS (Lack of dialogue box)
Reported by
tajoyc...@googlemail.com,
Dec 5 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9000.15.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.12 Safari/537.36 Platform: 9000.15.0 (Official Build) dev-channel link Steps to reproduce the problem: 1. Copy or move files and folders from the source to the destination with matching names 2. The files and folders will move correctly but not notify you that there will be duplicates 3. The duplicates will now be renamed with the suffix (1) or (2) depending on how many duplicates there are 4. This on larger scale causes havoc and chaos for file management on ChromeOS What is the expected behavior? When copying files or folders from one location to another, say for example you have a folder with backups of older files and you wish to copy the difference over from your device you are backing up, instead of copying each file and folder twice and suffixing them with (1) or (2) etc, the system should notify the user and ask them if they would like to proceed with copying and adding the suffix or if they would like to ignore the duplicates and cut them out of the command, proceeding only with the newer files and folders, thus eliminating all (1) and (2) suffix duplicates. What went wrong? In my example screenshot you can see that the folder I tried to copy from my device I am backing up was given a suffix at the end, this is not ideal on larger scale operations and I had to resort to using a Windows PC to perform my task. Did this work before? N/A Chrome version: 56.0.2924.12 Channel: dev OS Version: 9000.15.0 Flash Version: Shockwave Flash 23.0 r0 This is basic file transfer and should be integrated as soon as possible to make ChromeOS more viable, it makes it harder to justify using ChromeOS as my daily machine.
,
Jan 28 2017
,
Jan 30 2017
,
Nov 16 2017
,
Dec 12 2017
,
Feb 16 2018
<files-triage>
,
Feb 22 2018
<files-triage>
,
Feb 28 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ranjitkan@chromium.org
, Dec 5 2016