Add verbs API to file handlers. Modify the Chrome OS UI so that it displayes the internationalized …

chrome/common/extensions/api/file_manager_private.idl

Index: chrome/common/extensions/api/file_manager_private.idl
diff --git a/chrome/common/extensions/api/file_manager_private.idl b/chrome/common/extensions/api/file_manager_private.idl
index 1f9248643aabee8e8274ca0fe20cb77682eb7c3f..d5a724ad76a4328d5b98f85018a60a58929d0788 100644
--- a/chrome/common/extensions/api/file_manager_private.idl
+++ b/chrome/common/extensions/api/file_manager_private.idl
@@ -184,6 +184,14 @@ enum Source {
   system
 };
 
+// File handler verbs used to describe the action that an extension performs
+// over a file or directory.
+enum Verb {
+  open_with,
+  add_to,
+  pack_with
+};
+
 // A file task represents an action that the file manager can perform over the
 // currently selected files. See
 // chrome/browser/chromeos/extensions/file_manager/file_tasks.h for details
@@ -195,6 +203,10 @@ dictionary FileTask {
   // Task title (ex. App name).
   DOMString title;
 
+  // Task verb (ex. Open With). Can be empty string in case of no verb

[Devlin, 2016/05/20 21:08:16]

It can't be empty anymore, right?  It could just be omitted (which is already
indicated by the '?').  Also, the first part doesn't really tell much about how
it will be used.  Maybe add something like "The verb that will be used to
indicate what action the app will take" or something?

[cmihail, 2016/05/23 02:46:13]

Done. Though instead of empy, I did use Verb::VERB_NONE for the
FileBrowserHandler. Seems this is a default created value in the enum.

+  // (i.e. for FileBrowserHandler).
+  Verb? verb;
+
   // Task icon url (from chrome://extension-icon/...)
   DOMString iconUrl;