chrome/common/extensions/docs/templates/articles/experimental.html

<h1 class="page_title">chrome.experimental.* APIs</h1>

<h2 id="overview">
List of APIs
</h2>

{{^is_apps}}
<p class="doc-family extensions">
We'd like your <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">feedback</a>
on the following experimental APIs:
</p>
{{/is_apps}}

<ul>
  {{?is_apps}}
  {{#api_list.apps.experimental}}
  <li><a href="{{name}}.html">{{name}}</a></li>
  {{/}}
  {{:is_apps}}
  {{#api_list.extensions.experimental}}
  <li><a href="{{name}}.html">{{name}}</a></li>
  {{/}}
  {{/is_apps}}
</ul>

{{^is_apps}}
<p class="doc-family extensions">
Pay special attention to the following APIs,
which we expect to finalize soon:
<b>devtools</b>,
<b>permissions</b>,
For examples of using the experimental APIs, see
<a href="samples.html#experimental">Samples</a>.
</p>
{{/is_apps}}

<p class="warning">
<b>Caution:</b>
Don't depend on these experimental APIs.
They might disappear,
and they <em>will</em> change.
Also, the Chrome Web Store doesn't allow you to
upload items that use experimental APIs.
</p>


<h2 id="using">How to use experimental APIs</h2>

<ol>
  {{^is_apps}}
  <li class="doc-family extensions">
    Make sure you're using either
    <a href="http://tools.google.com/dlpage/chromesxs">Canary</a>
    (which you can use at the same time as other Chrome channels) or the
<a href="http://www.chromium.org/getting-involved/dev-channel">Dev channel</a>.
    Although the experimental APIs might work in other versions,
    we need your feedback on the latest incarnation of the APIs,
    which you can find in Canary and on the Dev channel.
  </li>
  {{/is_apps}}
  <li>
    Specify the "experimental"
    <a href="declare_permissions.html">permission</a>
    in your manifest, like this:
<pre>
"permissions": [
  <b>"experimental"</b>,
  ...
],
</pre>
  </li>
  <li>
    Enable the experimental API in your browser.
    You can do this in either of two ways:
    <ul>
      <li> Go to <b>chrome://flags</b>,
        find "Experimental Extension APIs",
        click its "Enable" link,
        and restart Chrome.
        From now on,
        unless you return to that page and disable experimental APIs,
        you'll be able to run extensions and apps that use experimental APIs.
      </li>
      <li> Specify the <b>--enable-experimental-extension-apis</b> flag
        each time you launch the browser.
        On Windows, you can do this by modifying
        the properties of the shortcut that you use to launch Google Chrome.
        For example:

<pre>
<em>path_to_chrome.exe</em> <b>--enable-experimental-extension-apis</b></pre>
      </li>
    </ul>
  </li>

  {{^is_apps}}
  <li class="doc-family extension">
    <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">Give us feedback!</a>
    Your comments and suggestions help us
    improve the APIs and decide
    which ones should move from experimental to supported.
  </li>
  {{/is_apps}}
</ol>

<h2 id="other">More APIs</h2>

<p>
For information on the standard APIs, see
<a href="api_index.html">chrome.* APIs</a> and
<a href="api_other.html">Other APIs</a>.
</p>