Merge 159156 - Extensions Docs Server: Fix headings with no IDs

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

 <h1>Formats: Manifest Files</h1>
 
 
 <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 44 matching lines @@
   "<a href="#permissions">permissions</a>": [...],
   "<a href="npapi.html">plugins</a>": [...],
   "<a href="#requirements">requirements</a>": {...},
   "<a href="autoupdate.html">update_url</a>": "http://<em>path/to/updateInfo</em>.xml",
   "<a href="#web_accessible_resources">web_accessible_resources</a>": [...],
   "<a href="#sandbox">sandbox</a>": [...]
 }
 </pre>
 
 
-<h2>Field details</h2>
+<h2 id="field_details">Field details</h2>
 
 <p>
 This section covers fields that aren't described in another page.
 For a complete list of fields,
 with links to where they're described in detail,
 see the <a href="#overview">Field summary</a>.
 </p>
 
 
 <h3 id="app">app</h3>
@@ skipping 168 matching lines @@
 </p>
 
 <p>
 The "disposition" is either "inline" or "window". Intents with "window" disposition will open a new tab when invoked. Intents with "inline" disposition will be displayed inside the intent picker when invoked.
 </p>
 
 <p>
 For more information on intents, refer to the <a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents specification</a> and <a href="http://www.webintents.org">webintents.org</a>.
 </p>
 
-<h4>Handling content types via intents</h4>
+<h4 id="content_types">Handling content types via intents</h4>
 
 <p>
 Web Intents can be registered as content type viewers. To do that, the action verb must be <a href="http://webintents.org/view">"http://webintents.org/view"</a>, and the content type must be a white-listed MIME type.
 </p>
 
 <table>
   <tr>
     <th>Whitelisted MIME types</th>
   </tr>
   <tr><td>application/rss+xml</td></tr>
@@ skipping 541 matching lines @@
 Prior to manifest version 2 all resources within an extension could be accessed
 from any page on the web. This allowed a malicious website to
 <a href="http://en.wikipedia.org/wiki/Device_fingerprint">fingerprint</a> the
 extensions that a user has installed or exploit vulnerabilities (for example
 <a href="http://en.wikipedia.org/wiki/Cross-site_scripting">XSS bugs</a>)within
 installed extensions. Limiting availability to only resources which are
 explicitly intended to be web accessible serves to both minimize the available
 attack surface and protect the privacy of users.
 </p>
 
-<h4>Default Availability</h4>
+<h4 id="availability">Default Availability</h4>
 
 <p>
 Resources inside of packages using <a href="#manifest_version"><code>manifest_version</code></a>
 2 or above are <strong>blocked by default</strong>, and must be whitelisted
 for use via this property.
 </p>
 
 <p>
 Resources inside of packages using <code>manifest_version</code> 1 are available
 by default, but <em>if</em> you do set this property, then it will be treated as
@@ skipping 61 matching lines @@
 goes into more detail about implementing a sandboxing workflow that enables use
 of libraries that would otherwise have issues executing under extension's
 <a href="../extensions/contentSecurityPolicy.html">default Content Security
 Policy</a>.
 </p>
 
 <p>
 Sandboxed page may only be specified when using
 <a href="#manifest_version"><code>manifest_version</code></a> 2 or above.
 </p>