summaryrefslogtreecommitdiffstats
path: root/content/ppapi_plugin
diff options
context:
space:
mode:
authorzelidrag@chromium.org <zelidrag@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-04-16 08:39:20 +0000
committerzelidrag@chromium.org <zelidrag@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-04-16 08:39:20 +0000
commit76066e5180a794b39d8f9550937b37b05f7793e8 (patch)
tree7b8a709544d0293808452ac622f01a0de195f013 /content/ppapi_plugin
parentcb23cdd5107b3f809f1a5a04a99098842364a15b (diff)
downloadchromium_src-76066e5180a794b39d8f9550937b37b05f7793e8.zip
chromium_src-76066e5180a794b39d8f9550937b37b05f7793e8.tar.gz
chromium_src-76066e5180a794b39d8f9550937b37b05f7793e8.tar.bz2
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@81865 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/ppapi_plugin')
0 files changed, 0 insertions, 0 deletions