1 <h1 class="page_title">chrome.experimental.* APIs</h1> 2 3 <h2 id="overview"> 4 List of APIs 5 </h2> 6 7 {{^is_apps}} 8 <p class="doc-family extensions"> 9 We'd like your <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">feedback</a> 10 on the following experimental APIs: 11 </p> 12 {{/is_apps}} 13 14 <ul> 15 {{?is_apps}} 16 {{#api_list.apps.experimental}} 17 <li><a href="{{name}}.html">{{name}}</a></li> 18 {{/}} 19 {{:is_apps}} 20 {{#api_list.extensions.experimental}} 21 <li><a href="{{name}}.html">{{name}}</a></li> 22 {{/}} 23 {{/is_apps}} 24 </ul> 25 26 {{^is_apps}} 27 <p class="doc-family extensions"> 28 Pay special attention to the following APIs, 29 which we expect to finalize soon: 30 <b>devtools</b>, 31 <b>permissions</b>, 32 For examples of using the experimental APIs, see 33 <a href="samples.html#experimental">Samples</a>. 34 </p> 35 {{/is_apps}} 36 37 <p class="warning"> 38 <b>Caution:</b> 39 Don't depend on these experimental APIs. 40 They might disappear, 41 and they <em>will</em> change. 42 Also, the Chrome Web Store doesn't allow you to 43 upload items that use experimental APIs. 44 </p> 45 46 47 <h2 id="using">How to use experimental APIs</h2> 48 49 <ol> 50 {{^is_apps}} 51 <li class="doc-family extensions"> 52 Make sure you're using either 53 <a href="http://tools.google.com/dlpage/chromesxs">Canary</a> 54 (which you can use at the same time as other Chrome channels) or the 55 <a href="http://www.chromium.org/getting-involved/dev-channel">Dev channel</a>. 56 Although the experimental APIs might work in other versions, 57 we need your feedback on the latest incarnation of the APIs, 58 which you can find in Canary and on the Dev channel. 59 </li> 60 {{/is_apps}} 61 <li> 62 Specify the "experimental" 63 <a href="declare_permissions.html">permission</a> 64 in your manifest, like this: 65 <pre> 66 "permissions": [ 67 <b>"experimental"</b>, 68 ... 69 ], 70 </pre> 71 </li> 72 <li> 73 Enable the experimental API in your browser. 74 You can do this in either of two ways: 75 <ul> 76 <li> Go to <b>chrome://flags</b>, 77 find "Experimental Extension APIs", 78 click its "Enable" link, 79 and restart Chrome. 80 From now on, 81 unless you return to that page and disable experimental APIs, 82 you'll be able to run extensions and apps that use experimental APIs. 83 </li> 84 <li> Specify the <b>--enable-experimental-extension-apis</b> flag 85 each time you launch the browser. 86 On Windows, you can do this by modifying 87 the properties of the shortcut that you use to launch Google Chrome. 88 For example: 89 90 <pre> 91 <em>path_to_chrome.exe</em> <b>--enable-experimental-extension-apis</b></pre> 92 </li> 93 </ul> 94 </li> 95 96 {{^is_apps}} 97 <li class="doc-family extension"> 98 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">Give us feedback!</a> 99 Your comments and suggestions help us 100 improve the APIs and decide 101 which ones should move from experimental to supported. 102 </li> 103 {{/is_apps}} 104 </ol> 105 106 <h2 id="other">More APIs</h2> 107 108 <p> 109 For information on the standard APIs, see 110 <a href="api_index.html">chrome.* APIs</a> and 111 <a href="api_other.html">Other APIs</a>. 112 </p> 113