| Index: chrome/common/extensions/docs/server2/templates/private/management_intro.html
|
| diff --git a/chrome/common/extensions/docs/server2/templates/private/management_intro.html b/chrome/common/extensions/docs/server2/templates/private/management_intro.html
|
| deleted file mode 100644
|
| index 1a11b01584df417e8805f3753d6709f538e1cdfc..0000000000000000000000000000000000000000
|
| --- a/chrome/common/extensions/docs/server2/templates/private/management_intro.html
|
| +++ /dev/null
|
| @@ -1,22 +0,0 @@
|
| -<!-- BEGIN AUTHORED CONTENT -->
|
| -<p id="classSummary">
|
| -The <code>chrome.management</code> module provides ways to manage the list of extensions/apps that are installed and running. It is particularly useful for extensions that <a href="override.html">override</a> the built-in New Tab page.
|
| -</p>
|
| -<h2 id="manifest">Manifest</h2>
|
| -<p>You must declare the "management" permission
|
| -in the <a href="manifest.html">extension manifest</a>
|
| -to use the management API.
|
| -For example:</p>
|
| -<pre>{
|
| - "name": "My extension",
|
| - ...
|
| - <b>"permissions": [
|
| - "management"
|
| - ]</b>,
|
| - ...
|
| -}</pre>
|
| -<p>
|
| -The one method that doesn't require the "management" permission is
|
| -<a href="#method-getPermissionWarningsByManifest"><code>getPermissionWarningsByManifest</code></a>
|
| -</p>
|
| -<!-- END AUTHORED CONTENT -->
|
|
|