Only show progress bar after 500ms

chrome/browser/resources/file_manager/js/file_copy_manager.js

Index: chrome/browser/resources/file_manager/js/file_copy_manager.js
diff --git a/chrome/browser/resources/file_manager/js/file_copy_manager.js b/chrome/browser/resources/file_manager/js/file_copy_manager.js
index d29bb526a4b58fc60e4f0d31a50c3e7fb81379ba..2262df57b4fdf7e8a343f8b5c1a5706916ca2a72 100644
--- a/chrome/browser/resources/file_manager/js/file_copy_manager.js
+++ b/chrome/browser/resources/file_manager/js/file_copy_manager.js
@@ -57,11 +57,14 @@ FileCopyManager.Task.prototype.setEntries = function(entries, callback) {
 }
 
 FileCopyManager.Task.prototype.takeNextEntry = function() {

[Rick Byers, 2012/03/09 21:45:45]

This function name is misleading now (you're not 'taking' anything).  Maybe it
should be 'get nextEntry'?

[bshe, 2012/03/12 00:13:34]

Done.

+  // We should keep the file in pending list and remove it after complete.
+  // Otherwise, if we try to get status in the middle of copying. The returned
+  // status is wrong (miss count the pasting item in totalItems).
   if (this.pendingDirectories.length)
-    return this.pendingDirectories.shift();
+    return this.pendingDirectories[0];
 
   if (this.pendingFiles.length)
-    return this.pendingFiles.shift();
+    return this.pendingFiles[0];
 
   return null;
 };
@@ -69,9 +72,11 @@ FileCopyManager.Task.prototype.takeNextEntry = function() {
 FileCopyManager.Task.prototype.markEntryComplete = function(entry, size) {
   if (entry.isDirectory) {
     this.completedDirectories.push(entry);
+    this.pendingDirectories.shift();

[Rick Byers, 2012/03/09 21:45:45]

You're implicitly assuming that 'entry' is still the next entry on the pending
list.  Are you sure that's always the case (I haven't looked at how this is
used)?  Regardless I'd suggest removing the risk of mismatch by either:
 1) checking that 'entry' still matches the next pending 
entry and throwing an exception or something if it doesn't, or
 2) removing entry wherever it occurs in the pending list (and possibly throwing
an exception if it occurs nowhere, but a no-op in that case probably isn't
terrible either).

[bshe, 2012/03/12 00:13:34]

It seems entry is targetEntry and shift function removes the corresponding
srcEntry. They will never be the same (src and target file path cant be the
same). 

From the code, it seems only after the targetEntry successfully wrote the file
system, the file copy manager then start to fetch next srcEntry in
pendingDirectories/Files list. So it should be safe here.

We can try to test if the entry is a targetEntry of srcEntry(entry returned from
shift function) to improve the safty here. But it probably wont be trivial and
we should probably create a new bug to track it. Given the risk if pretty low, I
am not sure if it's worth it though... 

   } else {
     this.completedFiles.push(entry);
     this.completedBytes += size;
+    this.pendingFiles.shift();
   }
 };
 
@@ -351,7 +356,9 @@ FileCopyManager.prototype.serviceNextTask_ = function(
   }
 
   function onEntryServiced(targetEntry, size) {
-    if (!targetEntry) {
+    // We should not dispatch a PROGRESS event when there is no pending items
+    // in the task.
+    if (task.pendingDirectories.length + task.pendingFiles.length == 0) {
       // All done with the entries in this task.
       if (task.deleteAfterCopy) {
         deleteOriginals()