Hide details panel when ESC is pressed.

ui/file_manager/file_manager/foreground/js/import_controller.js

Index: ui/file_manager/file_manager/foreground/js/import_controller.js
diff --git a/ui/file_manager/file_manager/foreground/js/import_controller.js b/ui/file_manager/file_manager/foreground/js/import_controller.js
index 2f744667cbb87dab22f42a7862ddde71916e6889..d09a5cdc36eca809dfd7e2b0e94509aa77720bb5 100644
--- a/ui/file_manager/file_manager/foreground/js/import_controller.js
+++ b/ui/file_manager/file_manager/foreground/js/import_controller.js
@@ -491,6 +491,20 @@ importer.RuntimeCommandWidget = function() {
 
   /** @private {function(!importer.ClickSource)} */
   this.clickListener_;
+
+  document.addEventListener('keydown', this.onKeyDown_.bind(this));

[hirono, 2015/02/24 07:40:45]

Is it OK to handle the event by document?
e.g. If we open context menu or dialog, the ESC key closes both the cloud import
banner and dialog box. Searching and renaming are also cancelled by ESC key.

[Steve McKay, 2015/02/25 21:22:13]

I think this is okay because any click outside of the panel will hide the
details panel.

Thoughts? Should we be just listening on the buttons? Then if user tabs away,
then hits escape...panel will still show.

+};
+
+/**
+ * Handle document scoped key-down events.

[hirono, 2015/02/24 07:40:45]

nit: Handles

[Steve McKay, 2015/02/25 21:22:13]

Done.

+ * @param {Event} event Key event.
+ * @private
+ */
+importer.RuntimeCommandWidget.prototype.onKeyDown_ = function(event) {
+  switch (util.getKeyModifiers(event) + event.keyIdentifier) {
+    case 'U+001B':
+      this.setDetailsVisible_(false);
+  }
 };
 
 /**