CrOS Files.app: fix the redraw logic on resize.

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 8048e9e8303b69fc87604b53cea44c8de5bf11df..55d1e70535e543343d976131ab78ced7b2d723ad 100644
--- a/chrome/browser/resources/file_manager/js/file_manager.js
+++ b/chrome/browser/resources/file_manager/js/file_manager.js
@@ -936,6 +936,7 @@ DialogType.isModal = function(type) {
       this.dialogDom_.querySelector('#app-name').innerText =
           chrome.runtime.getManifest().name;
       this.table_.normalizeColumns();
+      this.table_.redraw();
     }
   };
 
@@ -1410,9 +1411,11 @@ DialogType.isModal = function(type) {
         g.endBatchUpdates();
       }, 0);
     } else {
+      if (util.platform.newUI()) {
+        if (this.table_.clientWidth > 0)

[mtomasz, 2013/05/07 08:37:53]

Do we need this? What's the purpose of it? If the list is hidden then it is
empty, then normalizing doesn't cost anything.

[mtomasz, 2013/05/07 08:44:58]

OK, now I see. My repro steps for this are:
1. Open Files.app.
2. Open a picture.
3. Resize.
4. Close the gallery.

Result: empty.
Expected: not empty.

This still happens with this patch. It may be a race with closeFilePopup_'s
setTimeout(this.onResize_.bind(this), 0), I am not sure.

[mtomasz, 2013/05/07 09:15:34]

This check for clientWidth > 0 seem to me unnecessary.

[yoshiki, 2013/05/07 09:51:04]

We need this check. When this.table_.clientWidth=0, in
FileTableColumnModel.normalizeWidth(), the 'factor' variable is set to negative
value (l.49) and all the column widthes are set to negative value at (l.54).

+          this.table_.normalizeColumns();
+      }
       this.table_.redraw();
-      if (util.platform.newUI())
-        this.table_.normalizeColumns();
     }
 
     if (!util.platform.newUI())