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

Side by Side Diff: chrome/common/extensions/docs/privacy.html

Issue 9997001: Fix transient page sample extension to use 'runtime' API, which landed just (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 8 years, 8 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
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 341 matching lines...) Expand 10 before | Expand all | Expand 10 after
352 ... 352 ...
353 <b>"permissions": [ 353 <b>"permissions": [
354 "privacy" 354 "privacy"
355 ]</b>, 355 ]</b>,
356 ... 356 ...
357 }</pre> 357 }</pre>
358 <h2 id="usage">Usage</h2> 358 <h2 id="usage">Usage</h2>
359 <p> 359 <p>
360 Reading the current value of a Chrome setting is straightforward. You'll first 360 Reading the current value of a Chrome setting is straightforward. You'll first
361 need to find the property you're interested in, then you'll call 361 need to find the property you're interested in, then you'll call
362 <code>get()</code> on that object in order to retrieve it's current value and 362 <code>get()</code> on that object in order to retrieve its current value and
363 your extension's level of control. For example, to determine if Chrome's 363 your extension's level of control. For example, to determine if Chrome's
364 Autofill feature is enabled, you'd write: 364 Autofill feature is enabled, you'd write:
365 </p> 365 </p>
366 <pre>chrome.privacy.services.autofillEnabled.get({}, function(details) { 366 <pre>chrome.privacy.services.autofillEnabled.get({}, function(details) {
367 if (details.value) 367 if (details.value)
368 console.log('Autofill is on!'); 368 console.log('Autofill is on!');
369 else 369 else
370 console.log('Autofill is off!'); 370 console.log('Autofill is off!');
371 });</pre> 371 });</pre>
372 <p> 372 <p>
(...skipping 430 matching lines...) Expand 10 before | Expand all | Expand 10 after
803 _uff=0; 803 _uff=0;
804 urchinTracker(); 804 urchinTracker();
805 } 805 }
806 catch(e) {/* urchinTracker not available. */} 806 catch(e) {/* urchinTracker not available. */}
807 </script> 807 </script>
808 <!-- end analytics --> 808 <!-- end analytics -->
809 </div> 809 </div>
810 </div> <!-- /gc-footer --> 810 </div> <!-- /gc-footer -->
811 </div> <!-- /gc-container --> 811 </div> <!-- /gc-container -->
812 </body></html> 812 </body></html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698