Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(4736)

Unified Diff: chrome/common/extensions/docs/static/mediaGalleries.html

Issue 10821110: Rephrase some of the media galleries permission information. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Try again Created 8 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « chrome/common/extensions/docs/samples.json ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/common/extensions/docs/static/mediaGalleries.html
diff --git a/chrome/common/extensions/docs/static/mediaGalleries.html b/chrome/common/extensions/docs/static/mediaGalleries.html
index fc03902faab5afa56fd5bde91c1f6992e00491d5..fb808e20346d595a0ddb3bbfd77645ab0c46ff3c 100644
--- a/chrome/common/extensions/docs/static/mediaGalleries.html
+++ b/chrome/common/extensions/docs/static/mediaGalleries.html
@@ -14,17 +14,41 @@ locations, only media files will be present in the file system objects.
</P>
<h2 id="manifest">Manifest</h2>
-<p>You must declare the type of access to the media gallery you require
-in your extension's manifest to use the API. Currently only the
-"mediaGalleriesRead" permission is allowed. This permission does not
-currently trigger an install time permission prompt because it requires
-the user to grant permission at runtime.</p>
+<p>The media galleries API has two axes of permissions; the locations that
+can be accessed, and the type of access (read-only, read-write, add-files).</p>
-<p>
-You may also specify the "mediaGalleriesAllGalleries" permission to get
-access to all auto-detected media galleries on the user's computer. This
+<p>On the location axis, specifying no location-type permission means that
+no media galleries are accessible until the user grants permission to
+specific media galleries at runtime using the media gallery configuration
+dialog. This dialog can be programmatically triggered. Alternatively,
+specifying the "mediaGalleriesAllGalleries" permission grants access to all
+auto-detected media galleries on the user's computer. However, this
permission displays an install time prompt indicating that the extension
-will have access to all of the user's media files.
-</p>
+will have access to all of the user's media files.</p>
+
+<p>On the access type axis, the "mediaGalleriesRead" permission grants the
+extension the right to read files. This permission does not trigger an install
+time permission prompt because the user must still grant access to particular
+galleries, either with the "mediaGalleriesAllGalleries" permission or at
+runtime by using the media gallery management dialog. For example:</p>
+
+<pre>{
+ "name": "My extension",
+ ...
+ "permissions": [
+ <b>"mediaGalleriesAllGalleries"</b>
+ <b>"mediaGalleriesRead"</b>
+ ],
+ ...
+}</pre>
+
+<p>This set of permissions will trigger an install time permission prompt
+and let the extension read from all auto-detected media galleries on the
+user's computer. The user may add or remove galleries using the
+media gallery management dialog, after which the extension will be able
+to read all the media files from galleries that the user has selected.</p>
+
+<p>Currently "mediaGalleriesRead" is the only access type supported by
+this API. Read-write and add-file access with be implemented soon.</p>
<!-- END AUTHORED CONTENT -->
« no previous file with comments | « chrome/common/extensions/docs/samples.json ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698