[File Manager] Fix history state for GData folder navigation

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

Index: chrome/browser/resources/file_manager/js/file_manager.js
diff --git a/chrome/browser/resources/file_manager/js/file_manager.js b/chrome/browser/resources/file_manager/js/file_manager.js
index e33233d18d07d514f65ca03bfebd0dde6e082d63..874caf714a14ef276d54e09210f989ccccb655f9 100644
--- a/chrome/browser/resources/file_manager/js/file_manager.js
+++ b/chrome/browser/resources/file_manager/js/file_manager.js
@@ -3778,8 +3778,10 @@ FileManager.prototype = {
     // an object with 'path' and 'date' properties.
     this.lastLabelClick_ = null;
 
-    var dirEntry = event.newDirEntry;
-    this.updateLocation_(event.initial, dirEntry.fullPath);
+    // Sometimes we rescan the same directory, do not update the location then.

[SeRya, 2012/04/13 12:32:11]

I think it's a wrong fix.

Rescan doesn't cause directory change. There is no sense not only in updating
location, but also in updating buttons and breadcrumbs. 'directory-change'
mustn't be fired if event.newDirEntry.fullPath ==
event.previousDirEntry.fullPath.

Please, explain why two directory-change happen only on gdata? It sounds
suspicious for me. It could be a sign of a hidden bug.

+    if (event.newDirEntry.fullPath != event.previousDirEntry.fullPath) {
+      this.updateLocation_(event.initial, event.newDirEntry.fullPath);
+    }
 
     this.checkFreeSpace_(this.getCurrentDirectory());