diff options
| author | zelidrag@chromium.org <zelidrag@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-16 09:24:14 +0000 |
|---|---|---|
| committer | zelidrag@chromium.org <zelidrag@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-16 09:24:14 +0000 |
| commit | b6b805e9a9116fe454e11e652e5e8b3caac08c6b (patch) | |
| tree | 0d71d800e2682649249b864796a157754fb6222d /chrome/test/data/download_page2.html | |
| parent | fad613288e2dd25496cb7d8be90566bdbb76f8ec (diff) | |
| download | chromium_src-b6b805e9a9116fe454e11e652e5e8b3caac08c6b.zip chromium_src-b6b805e9a9116fe454e11e652e5e8b3caac08c6b.tar.gz chromium_src-b6b805e9a9116fe454e11e652e5e8b3caac08c6b.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@81869 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/test/data/download_page2.html')
0 files changed, 0 insertions, 0 deletions