chrome/common/extensions/docs/privacy.html - Issue 10642015: Basic setup for generating app docs

Unified Diff: chrome/common/extensions/docs/privacy.html

Issue 10642015: Basic setup for generating app docs (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 8 years, 6 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

Index: chrome/common/extensions/docs/privacy.html

diff --git a/chrome/common/extensions/docs/privacy.html b/chrome/common/extensions/docs/privacy.html

deleted file mode 100644

index d5f83fc0045e61f234d5016350b381543089768e..0000000000000000000000000000000000000000

--- a/chrome/common/extensions/docs/privacy.html

+++ /dev/null

@@ -1,858 +0,0 @@

-<!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:

- 1) The <head> information in this page is significant, should be uniform

- across api docs and should be edited only with knowledge of the

- templating mechanism.

- 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a

- browser, it will be re-generated from the template, json schema and

- authored overview content.

- 4) The <body>.innerHTML is also generated by an offline step so that this

- page may easily be indexed by search engines.

---><html xmlns="http://www.w3.org/1999/xhtml"><head>

- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

- <link href="css/ApiRefStyles.css" rel="stylesheet" type="text/css">

- <link href="css/print.css" rel="stylesheet" type="text/css" media="print">

- <script type="text/javascript" src="../../../third_party/jstemplate/jstemplate_compiled.js">

- </script>

- <script type="text/javascript" src="../../../../third_party/json_minify/minify-sans-regexp.js">

- </script>

- <script type="text/javascript" src="js/api_page_generator.js"></script>

- <script type="text/javascript" src="js/bootstrap.js"></script>

- <script type="text/javascript" src="js/sidebar.js"></script>

- <meta name="description" content="Documentation for the chrome.privacy module, which is part of the Google Chrome extension APIs."><title>Privacy - Google Chrome Extensions - Google Code</title></head>

- <body> <div id="devModeWarning" class="displayModeWarning">

- You are viewing extension docs in chrome via the 'file:' scheme: are you expecting to see local changes when you refresh? You'll need run chrome with --allow-file-access-from-files.

- </div>

- <div id="branchWarning" class="displayModeWarning">

- <span>WARNING: This is the <span id="branchName">BETA</span> documentation.

- It may not work with the stable release of Chrome.</span>

- <select id="branchChooser">

- <option>Choose a different version...

- </option><option value="">Stable

- </option><option value="beta">Beta

- </option><option value="dev">Dev

- </option><option value="trunk">Trunk

- </option></select>

- </div>

- <div id="unofficialWarning" class="displayModeWarning">

- <span>WARNING: This is unofficial documentation. It may not work with the

- current release of Chrome.</span>

- <button id="goToOfficialDocs">Go to the official docs</button>

- </div>

- <div id="gc-container" class="labs">

-

- <!-- In particular, sub-templates that recurse, must be used by allowing

- jstemplate to make a copy of the template in this section which

- are not operated on by way of the jsskip="true" -->

-

- <a id="top"></a>

- <div id="skipto">

- <a href="#gc-pagecontent">Skip to page content</a>

- <a href="#gc-toc">Skip to main navigation</a>

- </div>

-

- <table id="header" width="100%" cellspacing="0" border="0">

- <tbody><tr>

- <td valign="middle"><a href="http://code.google.com/"><img src="images/code_labs_logo.gif" height="43" width="161" alt="Google Code Labs" style="border:0; margin:0;"></a></td>

- <td valign="middle" width="100%" style="padding-left:0.6em;">

- <form action="http://www.google.com/cse" id="cse" style="margin-top:0.5em">

- <div id="gsc-search-box">

- <input type="hidden" name="cx" value="002967670403910741006:61_cvzfqtno">

- <input type="hidden" name="ie" value="UTF-8">

- <input type="text" name="q" value="" size="55">

- <input class="gsc-search-button" type="submit" name="sa" value="Search">

- <br>

- <span class="greytext">e.g. "page action" or "tabs"</span>

- </div>

- </form>

- <script type="text/javascript" src="https://www.google.com/jsapi"></script>

- <script type="text/javascript">google.load("elements", "1", {packages: "transliteration"});</script>

- <script type="text/javascript" src="https://www.google.com/coop/cse/t13n?form=cse&t13n_langs=en"></script>

- <script type="text/javascript" src="https://www.google.com/coop/cse/brand?form=cse&lang=en"></script>

- </td>

- </tr>

- </tbody></table>

- <div id="codesiteContent" class="">

- <a id="gc-topnav-anchor"></a>

- <div id="gc-topnav">

- <h1>Google Chrome Extensions (<a href="http://code.google.com/labs/">Labs</a>)</h1>

- <ul id="home" class="gc-topnav-tabs">

- <li id="home_link">

- <a href="index.html" title="Google Chrome Extensions home page">Home</a>

- </li>

- <li id="docs_link">

- <a href="docs.html" title="Official Google Chrome Extensions documentation">Docs</a>

- </li>

- <li id="faq_link">

- <a href="faq.html" title="Answers to frequently asked questions about Google Chrome Extensions">FAQ</a>

- </li>

- <li id="samples_link">

- <a href="samples.html" title="Sample extensions (with source code)">Samples</a>

- </li>

- <li id="group_link">

- <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions" title="Google Chrome Extensions developer forum">Group</a>

- </li>

- <li id="so_link">

- <a href="http://stackoverflow.com/questions/tagged/google-chrome-extension" title="[google-chrome-extension] tag on Stack Overflow">Questions?</a>

- </li>

- </ul>

- </div>

- <div class="g-section g-tpl-170">

-

- <div class="g-unit g-first" id="gc-toc">

- <ul>

- <li><a href="getstarted.html">Getting Started</a></li>

- <li><a href="overview.html">Overview</a></li>

- <li><a href="whats_new.html">What's New?</a></li>

- <li><h2><a href="devguide.html">Developer's Guide</a></h2>

- <ul>

- <li>Browser UI

- <ul>

- <li><a href="browserAction.html">Browser Actions</a></li>

- <li><a href="contextMenus.html">Context Menus</a></li>

- <li><a href="notifications.html">Desktop Notifications</a></li>

- <li><a href="omnibox.html">Omnibox</a></li>

- <li><a href="options.html">Options Pages</a></li>

- <li><a href="override.html">Override Pages</a></li>

- <li><a href="pageAction.html">Page Actions</a></li>

- </ul>

- </li>

- <li>Browser Interaction

- <ul>

- <li><a href="bookmarks.html">Bookmarks</a></li>

- <li><a href="cookies.html">Cookies</a></li>

- <li><a href="devtools.html">Developer Tools</a></li>

- <li><a href="events.html">Events</a></li>

- <li><a href="history.html">History</a></li>

- <li><a href="management.html">Management</a></li>

- <li><a href="tabs.html">Tabs</a></li>

- <li><a href="windows.html">Windows</a></li>

- </ul>

- </li>

- <li>Implementation

- <ul>

- <li><a href="a11y.html">Accessibility</a></li>

- <li><a href="background_pages.html">Background Pages</a></li>

- <li><a href="content_scripts.html">Content Scripts</a></li>

- <li><a href="xhr.html">Cross-Origin XHR</a></li>

- <li><a href="i18n.html">Internationalization</a></li>

- <li><a href="messaging.html">Message Passing</a></li>

- <li><a href="permissions.html">Optional Permissions</a></li>

- <li><a href="npapi.html">NPAPI Plugins</a></li>

- </ul>

- </li>

- <li>Finishing

- <ul>

- <li><a href="hosting.html">Hosting</a></li>

- <li><a href="external_extensions.html">Other Deployment Options</a></li>

- </ul>

- </li>

- </ul>

- </li>

- <li><h2><a href="apps.html">Packaged Apps</a></h2></li>

- <li><h2><a href="tutorials.html">Tutorials</a></h2>

- <ul>

- <li><a href="tut_debugging.html">Debugging</a></li>

- <li><a href="tut_analytics.html">Google Analytics</a></li>

- <li><a href="tut_oauth.html">OAuth</a></li>

- </ul>

- </li>

- <li><h2>Reference</h2>

- <ul>

- <li>Formats

- <ul>

- <li><a href="manifest.html">Manifest Files</a></li>

- <li><a href="match_patterns.html">Match Patterns</a></li>

- </ul>

- </li>

- <li><a href="permission_warnings.html">Permission Warnings</a></li>

- <li><a href="api_index.html">chrome.* APIs</a></li>

- <li><a href="api_other.html">Other APIs</a></li>

- </ul>

- </li>

- <li><h2><a href="samples.html">Samples</a></h2></li>

- <div class="line"> </div>

- <li><h2>More</h2>

- <ul>

- <li><a href="http://code.google.com/chrome/webstore/docs/index.html">Chrome Web Store</a></li>

- <li><a href="http://code.google.com/chrome/apps/docs/developers_guide.html">Hosted Apps</a></li>

- <li><a href="themes.html">Themes</a></li>

- </ul>

- </li>

- </ul>

- </div>

- <script>

- initToggles();

- </script>

- <div class="g-unit" id="gc-pagecontent">

- <div id="pageTitle">

- <h1 class="page_title">Privacy</h1>

- </div>

-

- <div id="toc">

- <h2>Contents</h2>

- <ol>

- <li>

- <a href="#manifest">Manifest</a>

- <ol>

- </ol>

- </li><li>

- <a href="#usage">Usage</a>

- <ol>

- </ol>

- </li><li>

- <a href="#examples">Examples</a>

- <ol>

- </ol>

- </li><li>

- <a href="#manifest">Manifest</a>

- <ol>

- </ol>

- </li><li>

- <a href="#usage">Usage</a>

- <ol>

- </ol>

- </li><li>

- <a href="#examples">Examples</a>

- <ol>

- </ol>

- </li>

- <li>

- <a href="#apiReference">API reference: chrome.privacy</a>

- <ol>

- <li>

- <a href="#properties">Properties</a>

- <ol>

- <li>

- <a href="#property-network">network</a>

- </li><li>

- <a href="#property-services">services</a>

- </li><li>

- <a href="#property-websites">websites</a>

- </li>

- </ol>

- </li>

- </ol>

- </li>

- </ol>

- </div>

-

-

-

- <div id="static"><div id="pageData-name" class="pageData">Privacy</div>

-

-<p id="classSummary">

- Use the <code>chrome.privacy</code> module to control usage of the features in

- Chrome that can affect a user's privacy. This module relies on the

- <a href="types.html#ChromeSetting">ChromeSetting prototype of the type API</a>

- for getting and setting Chrome's configuration.

-</p>

-<p class="note">

- The <a href="http://www.google.com/intl/en/landing/chrome/google-chrome-privacy-whitepaper.pdf">Chrome Privacy Whitepaper</a>

- gives background detail regarding the features which this API can control.

-</p>

-<h2 id="manifest">Manifest</h2>

-<p>

- You must declare the "privacy" permission in your extension's

- <a href="manifest.html">manifest</a> to use the API. For example:

-</p>

-<pre>{

- "name": "My extension",

- ...

- <b>"permissions": [

- "privacy"

- ]</b>,

- ...

-}</pre>

-<h2 id="usage">Usage</h2>

-<p>

- Reading the current value of a Chrome setting is straightforward. You'll first

- need to find the property you're interested in, then you'll call

- <code>get()</code> on that object in order to retrieve its current value and

- your extension's level of control. For example, to determine if Chrome's

- Autofill feature is enabled, you'd write:

-</p>

-<pre>chrome.privacy.services.autofillEnabled.get({}, function(details) {

- if (details.value)

- console.log('Autofill is on!');

- else

- console.log('Autofill is off!');

-});</pre>

-<p>

- Changing the value of a setting is a little bit more complex, simply because

- you first must verify that your extension can control the setting. The user

- won't see any change to her settings if your extension toggles a setting that

- is either locked to a specific value by enterprise policies

- (<code>levelOfControl</code> will be set to "not_controllable"), or if another

- extension is controlling the value (<code>levelOfControl</code> will be set to

- "controlled_by_other_extensions"). The <code>set()</code> call will succeed,

- but the setting will be immediately overridden. As this might be confusing, it

- is advisable to warn the user when the settings they've chosen aren't

- practically applied.

-</p>

-<p class="note">

- Full details about extensions' ability to control <code>ChromeSetting</code>s

- can be found under

- <a href="types.html#ChromeSetting">

- <code>chrome.types.ChromeSetting</code></a>.

-</p>

-<p>

- This means that you ought to use the <code>get()</code> method to determine

- your level of access, and then only call <code>set()</code> if your extension

- can grab control over the setting (in fact if your extension can't control the

- setting it's probably a good idea to visually disable the functionality to

- reduce user confusion):

-</p>

-<pre>chrome.privacy.services.autofillEnabled.get({}, function(details) {

- if (details.levelOfControl === 'controllable_by_this_extension') {

- chrome.privacy.services.autofillEnabled.set({ value: true }, function() {

- if (chrome.extension.lastError === undefined)

- console.log("Hooray, it worked!");

- else

- console.log("Sadness!", chrome.extension.lastError);

- }

-});</pre>

-<p>

- If you're interested in changes to a setting's value, add a listener to its

- <code>onChange</code> event. Among other uses, this will allow you to warn the

- user if a more recently installed extension grabs control of a setting, or if

- enterprise policy overrides your control. To listen for changes to Autofill's

- status, for example, the following code would suffice:

-</p>

-<pre>chrome.privacy.services.autofillEnabled.onChange.addListener(

- function (details) {

- // The new value is stored in `details.value`, the new level of control

- // in `details.levelOfControl`, and `details.incognitoSpecific` will be

- // `true` if the value is specific to Incognito mode.

- });</pre>

-<h2 id="examples">Examples</h2>

-<p>

- For example code, see the

- <a href="samples.html#privacy">Privacy API samples</a>.

-</p>

-<div id="pageData-name" class="pageData">Privacy</div>

-

-<p id="classSummary">

- Use the <code>chrome.privacy</code> module to control usage of the features in

- Chrome that can affect a user's privacy. This module relies on the

- <a href="types.html#ChromeSetting">ChromeSetting prototype of the type API</a>

- for getting and setting Chrome's configuration.

-</p>

-<p class="note">

- The <a href="http://www.google.com/intl/en/landing/chrome/google-chrome-privacy-whitepaper.pdf">Chrome Privacy Whitepaper</a>

- gives background detail regarding the features which this API can control.

-</p>

-<h2 id="manifest">Manifest</h2>

-<p>

- You must declare the "privacy" permission in your extension's

- <a href="manifest.html">manifest</a> to use the API. For example:

-</p>

-<pre>{

- "name": "My extension",

- ...

- <b>"permissions": [

- "privacy"

- ]</b>,

- ...

-}</pre>

-<h2 id="usage">Usage</h2>

-<p>

- Reading the current value of a Chrome setting is straightforward. You'll first

- need to find the property you're interested in, then you'll call

- <code>get()</code> on that object in order to retrieve its current value and

- your extension's level of control. For example, to determine if Chrome's

- Autofill feature is enabled, you'd write:

-</p>

-<pre>chrome.privacy.services.autofillEnabled.get({}, function(details) {

- if (details.value)

- console.log('Autofill is on!');

- else

- console.log('Autofill is off!');

-});</pre>

-<p>

- Changing the value of a setting is a little bit more complex, simply because

- you first must verify that your extension can control the setting. The user

- won't see any change to her settings if you extension toggles a setting that

- is either locked to a specific value by enterprise policies

- (<code>levelOfControl</code> will be set to "not_controllable"), or if another

- extension is controlling the value (<code>levelOfControl</code> will be set to

- "controlled_by_other_extensions"). The <code>set()</code> call will succeed,

- but the setting will be immediately overridden. As this might be confusing, it

- is advisable to warn the user when the settings they've chosen aren't

- practically applied.

-</p>

-<p class="note">

- Full details about extensions' ability to control <code>ChromeSetting</code>s

- can be found under

- <a href="types.html#ChromeSetting">

- <code>chrome.types.ChromeSetting</code></a>.

-</p>

-<p>

- This means that you ought to use the <code>get()</code> method to determine

- your level of access, and then only call <code>set()</code> if your extension

- can grab control over the setting (in fact if your extension can't control the

- setting it's probably a good idea to visibly disable the functionality to

- reduce user confusion):

-</p>

-<pre>chrome.privacy.services.autofillEnabled.get({}, function(details) {

- if (details.levelOfControl === 'controllable_by_this_extension') {

- chrome.privacy.services.autofillEnabled.set({ value: true }, function() {

- if (chrome.extension.lastError === undefined)

- console.log("Hooray, it worked!");

- else

- console.log("Sadness!", chrome.extension.lastError);

- }

-});</pre>

-<p>

- If you're interested in changes to a setting's value, add a listener to its

- <code>onChange</code> event. Among other uses, this will allow you to warn the

- user if a more recently installed extension grabs control of a setting, or if

- enterprise policy overrides your control. To listen for changes to Autofill's

- status, for example, the following code would suffice:

-</p>

-<pre>chrome.privacy.services.autofillEnabled.onChange.addListener(

- function (details) {

- // The new value is stored in `details.value`, the new level of control

- // in `details.levelOfControl`, and `details.incognitoSpecific` will be

- // `true` if the value is specific to Incognito mode.

- });</pre>

-<h2 id="examples">Examples</h2>

-<p>

- For example code, see the

- <a href="samples.html#privacy">Privacy API samples</a>.

-</p>

-

-</div>

-

- <div class="apiPage">

- <a name="apiReference"></a>

- <h2>API reference: chrome.privacy</h2>

-

- <div class="apiGroup">

- <a name="properties"></a>

- <h3 id="properties">Properties</h3>

- <div>

- <a name="property-network"></a>

- <h4>network</h4>

- <div class="summary">

-

- <span>chrome.privacy.</span><span>network</span>

- </div>

- <div>

- <dt>

- <var>network</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <span>object</span>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>Settings that influence Chrome's handling of network connections in general.</dd>

-

- <dd>

- <dl>

- <div>

- <dt>

- <var>networkPredictionEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome attempts to speed up your web browsing experience by pre-resolving DNS entries, prerendering sites (<code><link rel='prefetch' ...></code>), and preemptively opening TCP and SSL connections to servers. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </dl>

- </dd>

-

-

-

- </div>

- </div><div>

- <a name="property-services"></a>

- <h4>services</h4>

- <div class="summary">

-

- <span>chrome.privacy.</span><span>services</span>

- </div>

- <div>

- <dt>

- <var>services</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <span>object</span>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>Settings that enable or disable features that require third-party network services provided by Google and your default search provider.</dd>

-

- <dd>

- <dl>

- <div>

- <dt>

- <var>alternateErrorPagesEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome uses a web service to help resolve navigation errors. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>autofillEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome offers to automatically fill in forms. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>instantEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome automatically performs and displays search requests for text you type into the Omnibox as you type it. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>safeBrowsingEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome does its best to protect you from phishing and malware. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>searchSuggestEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome sends the text you type into the Omnibox to your default search engine, which provides predictions of websites and searches that are likely completions of what you've typed so far. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>spellingServiceEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome uses a web service to help correct spelling errors. This preference's value is a boolean, defaulting to <code>false</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>translationServiceEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome offers to translate pages that aren't in a language you read. This preference's value is a boolean, defaulting to <code>true</code>.</dd>

-

-

-

-

- </div>

- </dl>

- </dd>

-

-

-

- </div>

- </div><div>

- <a name="property-websites"></a>

- <h4>websites</h4>

- <div class="summary">

-

- <span>chrome.privacy.</span><span>websites</span>

- </div>

- <div>

- <dt>

- <var>websites</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <span>object</span>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>Settings that determine what information Chrome makes available to websites.</dd>

-

- <dd>

- <dl>

- <div>

- <dt>

- <var>thirdPartyCookiesAllowed</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If disabled, Chrome blocks third-party sites from setting cookies. The value of this preference is of type boolean, and the default value is <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>hyperlinkAuditingEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome sends auditing pings when requested by a website (<code><a ping></code>). The value of this preference is of type boolean, and the default value is <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>referrersEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a>types.ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd>If enabled, Chrome sends <code>referer</code> headers with your requests. Yes, the name of this preference doesn't match the misspelled header. No, we're not going to change it. The value of this preference is of type boolean, and the default value is <code>true</code>.</dd>

-

-

-

-

- </div>

- </div><div>

- <div>

- <dt>

- <var>protectedContentEnabled</var>

- <em>

-

- <div style="display:inline">

- (

- <span id="typeTemplate">

- <span>

- <a href="types.html#type-ChromeSetting">ChromeSetting</a>

- </span>

- )

- </div>

- </em>

- </dt>

- <dd><strong>Available on ChromeOS only</strong>: If enabled, Chrome provides a unique ID to plugins in order to run protected content. The value of this preference is of type boolean, and the default value is <code>true</code>.</dd>

-

-

-

-

- </div>

- </dl>

- </dd>

-

-

-

- </div>

- </div>

-

-

-

-

-

-

- </div>

- </div>

- </div>

- </div>

- <div id="gc-footer" --="">

- <div class="text">

- <p>

- Except as otherwise <a href="http://code.google.com/policies.html#restrictions">noted</a>,

- the content of this page is licensed under the <a rel="license" href="http://creativecommons.org/licenses/by/3.0/">Creative Commons

- Attribution 3.0 License</a>, and code samples are licensed under the

- <a rel="license" href="http://code.google.com/google_bsd_license.html">BSD License</a>.

- </p>

- <p>

- </p>

-

-<script src="https://www.google-analytics.com/urchin.js" type="text/javascript"></script>

-<script src="https://www.google-analytics.com/ga.js" type="text/javascript"></script>

-<script type="text/javascript">

- // chrome doc tracking

- try {

- var engdocs = _gat._getTracker("YT-10763712-2");

- engdocs._trackPageview();

- } catch(err) {}

- // code.google.com site-wide tracking

- try {

- _uacct="UA-18071-1";

- _uanchor=1;

- _uff=0;

- urchinTracker();

- }

- catch(e) {/* urchinTracker not available. */}

-</script>

-

- </div>

- </div>

- </div>

-</body></html>

« no previous file with comments | « chrome/common/extensions/docs/permissions.html ('k') | chrome/common/extensions/docs/proxy.html » ('j') | no next file with comments »