Files.app: Fix errors when launching Files.app via "chrome://files" (2)

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

Index: chrome/browser/resources/file_manager/js/util.js
diff --git a/chrome/browser/resources/file_manager/js/util.js b/chrome/browser/resources/file_manager/js/util.js
index 858eb4917c5ef695e1f91e6c9714327b41edabe1..978518d598ac56635be27da1e64c14f05e3c8c33 100644
--- a/chrome/browser/resources/file_manager/js/util.js
+++ b/chrome/browser/resources/file_manager/js/util.js
@@ -804,6 +804,16 @@ util.platform = {
   },
 
   /**
+   * @return {boolean} True if the files.app is running as AppsV2. False if

[mtomasz, 2013/06/04 06:38:44]

nit: the files.app -> Files.app (for consistency)

[yoshiki, 2013/06/04 06:57:34]

Done.

+   *     running via "chrome://files".
+   */
+  runningAsApps: function() {

[mtomasz, 2013/06/04 06:38:44]

This naming is confusing. Files.app in chrome://files is also an App V2. How
about renaming to 'runningInBrowser' ?

[yoshiki, 2013/06/04 06:57:34]

Done.

+    if (!util.platform.v2() || !util.platform.newUI())

[mtomasz, 2013/06/04 06:38:44]

Remove util.platform.newUI() check?

[yoshiki, 2013/06/04 06:57:34]

Done.

+      return false;
+    return (window.appID) ? true : false;

[mtomasz, 2013/06/04 06:38:44]

... -> return !!window.appID ?

[yoshiki, 2013/06/04 06:57:34]

Refactored.

+  },
+
+  /**
    * @return {boolean} True for the new ui.
    */
   newUI: function() {