chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html - Issue 10993029: Extensions Docs Server: Fix headings with no IDs

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html

Issue 10993029: Extensions Docs Server: Fix headings with no IDs (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: more descriptive ids Created 8 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « chrome/common/extensions/docs/templates/articles/sandboxingEval.html ('k') | chrome/common/extensions/docs/templates/intros/browserAction.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

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

diff --git a/chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html b/chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html

index 9bacc2f1a09d3bf394fcdef07c7cf0c0e42709da..5b02a5ed1762434051abcfdd10840bbfe2baac0c 100644

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

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

@@ -123,7 +123,7 @@ 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>

@@ -145,7 +145,7 @@ The browser actions API introduces some naming changes:</p>

</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 @@ The browser actions API introduces some naming changes:</p>

</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 @@ Many of these changes stem from Chrome’s adoption of

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 @@ 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

@@ -305,7 +305,7 @@ There are two ways to do this:

</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