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

Issues Search
    My Issues | Starred     Open | Closed | All

Side by Side Diff: chrome/common/extensions/docs/apps/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, 4 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 unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « chrome/common/extensions/docs/apps/experimental.html ('k') | chrome/common/extensions/docs/extensions/experimental.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
2 1) The <head> information in this page is significant, should be uniform 2 1) The <head> information in this page is significant, should be uniform
3 across api docs and should be edited only with knowledge of the 3 across api docs and should be edited only with knowledge of the
4 templating mechanism. 4 templating mechanism.
5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
6 browser, it will be re-generated from the template, json schema and 6 browser, it will be re-generated from the template, json schema and
7 authored overview content. 7 authored overview content.
8 4) The <body>.innerHTML is also generated by an offline step so that this 8 4) The <body>.innerHTML is also generated by an offline step so that this
9 page may easily be indexed by search engines. 9 page may easily be indexed by search engines.
10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>
(...skipping 181 matching lines...) Expand 10 before | Expand all | Expand 10 after
192 The media galleries API allows you to access media files (images, 192 The media galleries API allows you to access media files (images,
193 video, audio) from the user's local disks (with the user's consent). 193 video, audio) from the user's local disks (with the user's consent).
194 </p> 194 </p>
195 <p> 195 <p>
196 Using the API, you can prompt the user for permission to access the media 196 Using the API, you can prompt the user for permission to access the media
197 galleries. The permission dialog will contain common media locations for 197 galleries. The permission dialog will contain common media locations for
198 the platform and will allow the user to add additional locations. From those 198 the platform and will allow the user to add additional locations. From those
199 locations, only media files will be present in the file system objects. 199 locations, only media files will be present in the file system objects.
200 </p> 200 </p>
201 <h2 id="manifest">Manifest</h2> 201 <h2 id="manifest">Manifest</h2>
202 <p>You must declare the type of access to the media gallery you require 202 <p>The media galleries API has two axes of permissions; the locations that
203 in your extension's manifest to use the API. Currently only the 203 can be accessed, and the type of access (read-only, read-write, add-files).</p>
204 "mediaGalleriesRead" permission is allowed. This permission does not 204 <p>On the location axis, specifying no location-type permission means that
205 currently trigger an install time permission prompt because it requires 205 no media galleries are accessible until the user grants permission to
206 the user to grant permission at runtime.</p> 206 specific media galleries at runtime using the media gallery configuration
207 <p> 207 dialog. This dialog can be programmatically triggered. Alternatively,
208 You may also specify the "mediaGalleriesAllGalleries" permission to get 208 specifying the "mediaGalleriesAllGalleries" permission grants access to all
209 access to all auto-detected media galleries on the user's computer. This 209 auto-detected media galleries on the user's computer. However, this
210 permission displays an install time prompt indicating that the extension 210 permission displays an install time prompt indicating that the extension
211 will have access to all of the user's media files. 211 will have access to all of the user's media files.</p>
212 </p> 212 <p>On the access type axis, the "mediaGalleriesRead" permission grants the
213 extension the right to read files. This permission does not trigger an install
214 time permission prompt because the user must still grant access to particular
215 galleries, either with the "mediaGalleriesAllGalleries" permission or at
216 runtime by using the media gallery management dialog. For example:</p>
217 <pre>{
218 "name": "My extension",
219 ...
220 "permissions": [
221 <b>"mediaGalleriesAllGalleries"</b>
222 <b>"mediaGalleriesRead"</b>
223 ],
224 ...
225 }</pre>
226 <p>This set of permissions will trigger an install time permission prompt
227 and let the extension read from all auto-detected media galleries on the
228 user's computer. The user may add or remove galleries using the
229 media gallery management dialog, after which the extension will be able
230 to read all the media files from galleries that the user has selected.</p>
231 <p>Currently "mediaGalleriesRead" is the only access type supported by
232 this API. Read-write and add-file access with be implemented soon.</p>
213 <!-- END AUTHORED CONTENT --> 233 <!-- END AUTHORED CONTENT -->
214 </div> 234 </div>
215 <!-- API PAGE --> 235 <!-- API PAGE -->
216 <div class="apiPage"> 236 <div class="apiPage">
217 <a name="apiReference"></a> 237 <a name="apiReference"></a>
218 <h2>API reference: chrome.mediaGalleries</h2> 238 <h2>API reference: chrome.mediaGalleries</h2>
219 <!-- PROPERTIES --> 239 <!-- PROPERTIES -->
220 <!-- /apiGroup --> 240 <!-- /apiGroup -->
221 <!-- METHODS --> 241 <!-- METHODS -->
222 <div id="methodsTemplate" class="apiGroup"> 242 <div id="methodsTemplate" class="apiGroup">
(...skipping 189 matching lines...) Expand 10 before | Expand all | Expand 10 after
412 _uff=0; 432 _uff=0;
413 urchinTracker(); 433 urchinTracker();
414 } 434 }
415 catch(e) {/* urchinTracker not available. */} 435 catch(e) {/* urchinTracker not available. */}
416 </script> 436 </script>
417 <!-- end analytics --> 437 <!-- end analytics -->
418 </div> 438 </div>
419 </div> <!-- /gc-footer --> 439 </div> <!-- /gc-footer -->
420 </div> <!-- /gc-container --> 440 </div> <!-- /gc-container -->
421 </body></html> 441 </body></html>
OLDNEW
« no previous file with comments | « chrome/common/extensions/docs/apps/experimental.html ('k') | chrome/common/extensions/docs/extensions/experimental.html » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698