Upstream version 9.38.198.0

[platform/framework/web/crosswalk.git] / src / chrome / common / extensions / docs / templates / articles / settings_override.html

diff --git a/src/chrome/common/extensions/docs/templates/articles/settings_override.html b/src/chrome/common/extensions/docs/templates/articles/settings_override.html
index f00167a..c9b723b 100644 (file)
--- a/src/chrome/common/extensions/docs/templates/articles/settings_override.html
+++ b/src/chrome/common/extensions/docs/templates/articles/settings_override.html
@@ -8,8 +8,13 @@ Settings overrides are a way for extensions to override selected Chrome settings
 <p>
 Here is an example how <a href="#homepage">homepage</a>, <a
 href="#search_provider">search provider</a> and <a href="#startup_pages">startup
-pages</a> can be modified in the <a href="manifest.html">extension
-manifest</a>.</p>
+pages</a> can be modified in the <a href="manifest">extension
+manifest</a>. Web sites used in the settings API must be
+<a href="https://support.google.com/webmasters/answer/35179">verified</a> (via
+Webmaster Tools) as being associated with that item in the Chrome Web Store.
+Note that if you verify ownership for a domain (for example, http://example.com)
+you can use any subdomain or page (for example, http://app.example.com or
+http://example.com/page.html) within your extension.</p>
 
 <pre>{
   "name": "My extension",
@@ -46,6 +51,32 @@ manifest</a>.</p>
 <code>search_provider</code>, and <code>startup_pages</code> are only enabled
 in the Chrome Dev release.</p>
 
+<h2 id="customizing">Customizing values</h2>
+<p>Values in the manifest can be customized in the following ways:</p>
+<ul>
+  <li>
+  All values of the <code>search_provider</code>, <code>homepage</code> and
+  <code>startup_pages</code> properties can be localized using the
+  $(ref:i18n chrome.i18n API).
+  </li>
+  <li>
+  For <a href="http://developer.chrome.com/extensions/external_extensions">external extensions</a>,
+  the <code>search_provider</code>, <code>homepage</code> and
+  <code>startup_pages</code> URL values can be parametrized using a registry key.
+  A new registry entry should be created next to the "update_url" key (see
+  instructions <a href="http://developer.chrome.com/extensions/external_extensions#registry">here</a>).
+  The value name is "install_parameter", the value data is an arbitrary string:
+  <pre>{
+    "update_url": "https://clients2.google.com/service/update2/crx",
+    "install_parameter": "Value"
+  }</pre>
+  All occurrences of the substring "__PARAM__" in the manifest URLs will be
+  substituted with the "install_parameter" value. If “install_parameter” is
+  absent, occurrences of "__PARAM__" are removed. Note that "__PARAM__" cannot
+  be part of the hostname. It needs to occur after the first '/' in the URL.
+  </li>
+</ul>
+
 <h2 id="reference">Reference</h2>
 <p>
 An extension can override one or more of the following properties in the
@@ -53,7 +84,7 @@ manifest:
 </p>
 
 <ul>
-{{#f:apis.manifestTypes.byName.ChromeSettingsOverrides.properties}}
+{{#f:apis.extensions.manifestTypes.byName.ChromeSettingsOverrides.properties}}
   <li>
   <p id="{{f.name}}"><b><code>{{f.name}}</code> ({{+partials.variable_type type:f/}})</b></p>
   <p>{{f.description}}</p>