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

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

 <h1>Tutorial: Migrate to Manifest V2</h1>
 
 <p>
 Manifest version 1 was deprecated in Chrome 18,
 and support will be phased out according to the
 <a href="manifestVersion.html">manifest version 1 support schedule</a>.
 The changes from version 1 to version 2
 fall under two broad categories:
 API changes and Security changes. 
 </p>
@@ skipping 105 matching lines @@
 </ul>
 
 <h2 id="api-summary">Summary of API changes</h2>
 
 <p>
 Manifest version 2 introduces a few changes
 to the browser action and page action APIs,
 and replaces a few old APIs with newer ones.
 </p>
 
-<h3>Changes to browser actions</h3>
+<h3 id="browser_actions">Changes to browser actions</h3>
 
 <p>
 The browser actions API introduces some naming changes:</p>
 
 <ul>
   <li>The <code>browser_actions</code> and
     <code>chrome.browserActions</code> properties have been replaced
     with their singular counterparts <code>browser_action</code>
     and <code>chrome.browserAction</code>.</li>
   <li>Under the old <code>browser_actions</code> property,
     there were <code>icons</code>, <code>name</code>, and
     <code>popup</code> properties.
     These have been replaced with:</li>
   <ul>
     <li><code>default_icon</code> for the browser action badge icon</li>
     <li><code>default_name</code> for the text that appears in the tooltip when you hover over the badge</li>
     <li><code>default_popup</code> for the HTML page that represents the UI
       for the browser action (and this must now be a string, it cannot be an object)</li>
   </ul>
 </ul>
 
-<h3>Changes to page actions</h3>
+<h3 id="page_actions">Changes to page actions</h3>
 
 <p>Similar to the changes for browser actions,
   the page actions API has also changed:</p>
 <ul>
   <li>The <code>page_actions</code> and <code>chrome.pageActions</code> properties
     have been replaced with their singular counterparts
     <code>page_action</code> and <code>chrome.pageAction</code>.</li>
   <li>Under the old <code>page_actions</code> property,
     there were <code>icons</code>, <code>name</code>,
     and <code>popup</code> properties.
     These have been replaced with:</li>
   <ul>
     <li><code>default_icon</code> for the page action badge icon</li>
     <li><code>default_name</code> for the text
       that appears in the tooltip when you hover over the badge</li>
     <li><code>default_popup</code> for the HTML page
       that represents the UI for the page action
       (and this must now be a string, it cannot be an object)</li>
   </ul>
 </ul>
 
-<h3>Removed and changed APIs</h3>
+<h3 id="removed_and_changed">Removed and changed APIs</h3>
 
 <p>
 A few extension APIs have been removed and replaced with new counterparts:
 </p>
 
 <ul>
   <li>The <code>background_page</code> property has been replaced
     by <a href="background_pages.html">background</a>.</li>
   <li>The <code>chrome.self</code> property has been removed,
     use <code>chrome.extension</code>.</li>
   <li>The <code>Port.tab</code> property has been replaced
     with <code>Port.sender</code>.</li>
   <li>The <code>chrome.extension.getTabContentses()</code> and the
     <code>chrome.extension.getExtensionTabs()</code> APIs have been replaced
     by <code>chrome.extension.getViews( { “type” : “tab” } )</code>.</li>
 </ul>
 
 <h2 id="security-summary">Summary of security changes</h2>
 
 <p>
 There are a number of security-related changes
 that accompany the move from manifest version 1 to version 2.
 Many of these changes stem from Chrome’s adoption of
 <a href="contentSecurityPolicy.html#H3-1">Content Security Policy</a>;
 you should read more about this policy to understand its implications.
 </p>
 
-<h3>Inline scripts and event handlers disallowed</h3>
+<h3 id="inline_scripts">Inline scripts and event handlers disallowed</h3>
 
 <p>
 Due to the use of <a href="contentSecurityPolicy.html">Content Security Policy</a>,
 you can no longer use &lt;script> tags that are inline with the HTML content.
 These must be moved to external JS files.
 In addition, inline event handlers are also not supported.
 For example, suppose you had the following code in your extension:
 </p>
 
 <pre>
@@ skipping 36 matching lines @@
 window.addEventListener(“load”, initialize);
 ...
 document.getElementById(“button1”).addEventListener(“click”,handleClick);
 </pre>
 
 <p>
 This is a much cleaner way of separating
 your extension’s behavior from its user interface markup.
 </p>
 
-<h3>Embedding content</h3>
+<h3 id="embedding">Embedding content</h3>
 
 <p>
 There are some scenarios where your extension might embed content
 that can be used externally or come from an external source. 
 </p>
 
 <p>
 <strong>Extension content in web pages:</strong><br>
 If your extension embeds resources (like images, script, CSS styles, etc)
 that are used in content scripts that are injected into web pages,
@@ skipping 32 matching lines @@
       <pre>
         { // manifest file
           ...,
           "content_security_policy": "script-src 'self'
           <strong>https://ssl.google-analytics.com</strong>; object-src 'self'",
           ...
         }
       </pre></li>
 </ol>
 
-<h3>Using dynamic script evaluation</h3>
+<h3 id="using">Using dynamic script evaluation</h3>
 
 <p>
 Perhaps one of the biggest changes in the new manifest v2 scheme is
 that extensions can no longer use dynamic script evaluation techniques like
 <code>eval()</code> or new <code>Function()</code>,
 or pass strings of JS code to functions
 that will cause an <code>eval()</code> to be used,
 like <code>setTimeout()</code>.
 In addition, certain commonly used JavaScript libraries,
 such as Google Maps and certain templating libraries,
@@ skipping 30 matching lines @@
 For more information about using sandboxing to isolate unsafe code,
 read the <a href="sandboxingEval.html">sandboxing eval</a> article.
 You can learn more about Content Security Policy
 by visiting our extensions-related tutorial and a
 <a href="http://www.html5rocks.com/en/tutorials/security/content-security-policy/">good introduction on HTML5Rocks</a>.
 </p>