| Index: chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html
|
| ===================================================================
|
| --- chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html (revision 159604)
|
| +++ chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html (working copy)
|
| @@ -123,7 +123,7 @@
|
| 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>
|
| @@ -145,7 +145,7 @@
|
| </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>
|
| @@ -167,7 +167,7 @@
|
| </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:
|
| @@ -195,7 +195,7 @@
|
| 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>,
|
| @@ -252,7 +252,7 @@
|
| 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
|
| @@ -305,7 +305,7 @@
|
| </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
|
|
|