chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html - Issue 14273041: Doc server manifest page generation

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 14273041: Doc server manifest page generation (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: fix imports Created 7 years, 5 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/override.html ('k') | chrome/common/extensions/docs/templates/articles/whats_new.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 7a28649c02935f139c1b6f6e4304d8bd6f79c3cd..6e39c1a929b8b26ea6def79fdef76443409e0be3 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

@@ -83,13 +83,13 @@ followed by more detailed summaries of what these changes mean and why they were

that need to access resources (like images and scripts)

that are contained in the extension’s package?</li>

<ul>

- <li>Define the <a href="manifest.html#web_accessible_resources">web_accessible_resources</a>

+ <li>Define the <a href="manifest/web_accessible_resources.html">web_accessible_resources</a>

property and list the resources

(and optionally a separate Content Security Policy for those resources).</li>

</ul>

<li>Does your extension embed external Web pages?</li>

<ul>

- <li>Define the <a href="manifest.html#sandbox">sandbox</a> property.</li>

+ <li>Define the <a href="manifest/sandbox.html">sandbox</a> property.</li>

</ul>

<li>Is your code or library using <code>eval()</code>, new <code>Function()</code>,

<code>innerHTML</code>, <code>setTimeout()</code>, or otherwise passing strings

@@ -264,7 +264,7 @@ that can be used externally or come from an external source.

If your extension embeds resources (like images, script, CSS styles, etc)

that are used in content scripts that are injected into web pages,

you need to use the

-<a href="manifest.html#web_accessible_resources">web_accessible_resources</a> property

+<a href="manifest/web_accessible_resources.html">web_accessible_resources</a> property

to whitelist these resources so that external Web pages can use them:

</p>