Merge 76274 - Add info about "background" permission (new for M10)....

chrome/common/extensions/docs/static/manifest.html

 <div id="pageData-name" class="pageData">Formats: Manifest Files</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>
 Every extension, installable web app, and theme has a
 <a href="http://www.json.org">JSON</a>-formatted manifest file,
 named <code>manifest.json</code>,
 that provides important information.
 </p>
 
@@ skipping 279 matching lines @@
 </pre>
 
 <p>
 The following table lists the permissions an extension
 or packaged app can use.
 </p>
 
 <p class="note">
 <strong>Note:</strong>
 Hosted apps can use the
-"geolocation", "notifications", and "unlimitedStorage" permissions,
+"background", "geolocation", "notifications", and "unlimitedStorage" permissions,
 but not any other permissions listed in this table.
 </p>
 
 <table>
 <tr>
   <th> Permission </th> <th> Description </th>
 </tr>
 <tr>
   <td> <em>match pattern</em> </td>
   <td> Specifies a <em>host permission</em>.
        Required if the extension wants to interact
        with the code running on pages.
        Many extension capabilities, such as
        <a href="xhr.html">cross-origin XMLHttpRequests</a>,
        <a href="content_scripts.html#pi">programmatically injected
        content scripts</a>, and <a href="cookies.html">the cookies API</a>
        require host permissions. For details on the syntax, see
        <a href="match_patterns.html">Match Patterns</a>.
   </td>
 </tr>
 <tr>
+  <td> "background" </td>
+  <td> <p>
+       Makes Chrome start up early and and shut down late,
+       so that apps and extensions can have a longer life.
+       </p>
+
+       <p>
+       When any installed hosted app, packaged app, or extension
+       has "background" permission, Chrome runs (invisibly)
+       as soon as the user logs into their computer&mdash;before
+       the user launches Chrome.
+       The "background" permission also makes Chrome continue running
+       (even after its last window is closed)
+       until the user explicitly quits Chrome.
+       </p>
+
+       <p class="note">
+       <b>Note:</b>
+       Disabled apps and extensions
+       are treated as if they aren't installed.
+       </p>
+
+       <p>
+       You typically use the "background" permission with a
+       <a href="background_pages.html">background page</a>
+       or (for hosted apps) a
+       <a href="http://code.google.com/chrome/apps/docs/background.html">background window</a>.
+       </p>
+       </td>
+</tr>
+<tr>
   <td> "bookmarks" </td>
   <td> Required if the extension uses the
        <a href="bookmarks.html">chrome.bookmarks</a> module. </td>
 </tr>
 <tr>
   <td> "chrome://favicon/" </td>
   <td> Required if the extension uses the
        "chrome://favicon/<em>url</em>" mechanism
        to display the favicon of a page.
        For example, to display the favicon of http://www.google.com/,
@@ skipping 115 matching lines @@
 A missing integer is equal to zero.
 For example, 1.1.9.9999 is newer than 1.1.
 </p>
 
 <p>
 For more information, see
 <a href="autoupdate.html">Autoupdating</a>.
 </p>
 
 <!-- [PENDING: Possibly: point to the store/dashboard and make a big deal of the fact that autoupdating is free if you use them.] -->