Home | History | Annotate | Download | only in static 
      1 <div id="pageData-name" class="pageData">chrome.experimental.* APIs</div>
      2 
      3 <p>
      4 We'd like your <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">feedback</a>
      5 on the following experimental APIs:
      6 </p>
      7 
      8 <ul>
      9   <li jsselect="experimentalAPIs();">
     10   <a jsvalues=".href: $this + '.html'" jscontent="$this"></a></li>
     11 </ul>
     12 
     13 <p class="warning">
     14 <b>Caution:</b>
     15 Don't depend on these experimental APIs.
     16 They might disappear,
     17 and they <em>will</em> change.
     18 Also, the Chrome Developer Dashboard doesn't allow you to
     19 upload extensions that use experimental APIs.
     20 </p>
     21 
     22 <h2 id="using">How to use experimental APIs</h2>
     23 
     24 <ol>
     25   <li>
     26     Make sure you're using the
     27 <a href="http://www.chromium.org/getting-involved/dev-channel">Dev channel</a>
     28     of Google Chrome.
     29     Although the experimental APIs might work in other versions,
     30     we need your feedback on the latest incarnation of the APIs,
     31     which you can find on the Dev channel.
     32   </li>
     33   <li>
     34     Using the
     35     <a href="http://code.google.com/chrome/extensions/dev/experimental.html">API documentation for the Dev channel</a>,
     36     write the code for your extension.
     37   </li>
     38   <li>
     39     Specify the "experimental"
     40     <a href="manifest.html#permissions">permission</a>
     41     in your extension's manifest, like this:
     42 <pre>
     43 "permissions": [
     44   <b>"experimental"</b>,
     45   ...
     46 ],
     47 </pre>
     48   </li>
     49   <li>
     50     Enable the experimental API in your browser.
     51     You can do this in either of two ways:
     52     <ul>
     53       <li> Go to <b>chrome://flags</b>,
     54         find "Experimental Extension APIs",
     55         click its "Enable" link,
     56         and restart Chrome.
     57         From now on,
     58         unless you return to that page and disable experimental APIs,
     59         you'll be able to run extensions that use experimental APIs.
     60       </li>
     61       <li> Specify the <b>--enable-experimental-extension-apis</b> flag
     62         each time you launch the browser.
     63         On Windows, you can do this by modifying
     64         the properties of the shortcut that you use to launch Google Chrome.
     65         For example:
     66 
     67 <pre>
     68 <em>path_to_chrome.exe</em> <b>--enable-experimental-extension-apis</b></pre>
     69       </li>
     70     </ul>
     71   </li>
     72 
     73   <li>
     74     <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">Give us feedback!</a>
     75     Your comments and suggestions help us
     76     improve the APIs and decide
     77     which ones should move from experimental to supported.
     78   </li>
     79 </ol>
     80 
     81 <h2 id="other">More information</h2>
     82 
     83 <p>
     84 For information on the standard APIs that extensions can use, see
     85 <a href="api_index.html">chrome.* APIs</a> and
     86 <a href="api_other.html">Other APIs</a>.
     87 </p>
     88