New fileBrowserPrivate and fileHandler APIs added + plus magic needed to safely hand over access to local file system elements from content extension to 3rd party extension.

As agreed with aa@ and asargent@, this new API defines following event:

chrome.fileHandler.onExecute.addListener(function(id, file_entries) {
}

This event is invoked when user selects files in ChromeOS file browser.

The extension needs to register itself as file content hanlder with following manifest changes:
...
"file_browser_actions": [
{
"id" : "ActionIdentifier",
"default_title" : "Action title",
"default_icon" : "icon.png",
"file_filters" : [ "filesystem:*.jpeg", ... ]
}
...
],
...



BUG=chromium-os:11996
TEST=ExtensionApiTest.FileBrowserTest, ExtensionManifestTest.FileBrowserActions 
Review URL: http://codereview.chromium.org/6749021

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81869 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 4 deletions

diff --git a/chrome/common/extensions/extension_unittest.cc b/chrome/common/extensions/extension_unittest.cc
index 905fd5c..131f144 100644
--- a/chrome/common/extensions/extension_unittest.cc
+++ b/chrome/common/extensions/extension_unittest.cc
@@ -1025,10 +1025,6 @@ TEST(ExtensionTest, PermissionMessages) {
   // so we won't prompt for it for now.
   skip.insert(Extension::kFileBrowserHandlerPermission);
 
-  // This permission requires explicit user action (context menu handler)
-  // so we won't prompt for it for now.
-  skip.insert(Extension::kFileSystemPermission);
-
   // If you've turned on the experimental command-line flag, we don't need
   // to warn you further.
   skip.insert(Extension::kExperimentalPermission);