diff options
| author | hirono@chromium.org <hirono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-18 11:08:29 +0000 |
|---|---|---|
| committer | hirono@chromium.org <hirono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-18 11:08:29 +0000 |
| commit | ca43f4da1465d829439f68184f01448b42206483 (patch) | |
| tree | 6058f93a5407b0d3f8a8f6475bb8c9fdf8b9b349 /ui/app_list | |
| parent | c69bc8871ffb663cfb4bc9c90c7368a9a44b684e (diff) | |
| download | chromium_src-ca43f4da1465d829439f68184f01448b42206483.zip chromium_src-ca43f4da1465d829439f68184f01448b42206483.tar.gz chromium_src-ca43f4da1465d829439f68184f01448b42206483.tar.bz2 | |
Files.app: Fixed copying/moving from drive to download.
If FileCopyManager traverses child entries in the task, the entries may depend
on the other entries. So we should keep the order of entries to processing.
On the other hand, if FileCopyManager does not traverse child entries, the
entries independs on each other. But in this case, the files may be moved from
search results, where a parent directories may be moved ealier than its child
elements is occured. To avoid the case, we should process the deepest element.
When entries are moving from the search results, the child entries does not
traversed recursively. However we have sorted the entry list to process the
deepest element in original codes even if FileCopyManager traverses child
entries recursively. Changing the order of traversed entries causes errors. This
CL fix the problem so that the entry list does not sorted when the entries are
treversed.
BUG=244486
TEST=manually
Review URL: https://chromiumcodereview.appspot.com/15648014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@206929 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/app_list')
0 files changed, 0 insertions, 0 deletions