chrome/common/extensions/docs/templates/articles/app_external.html - Issue 219213007: Remove .html extension from links

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

Issue 219213007: Remove .html extension from links (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 6 years, 8 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

« chrome/common/extensions/docs/templates/articles/app_codelab8_webresources.html ('K') | « chrome/common/extensions/docs/templates/articles/app_deprecated.html ('k') | chrome/common/extensions/docs/templates/articles/app_frameworks.html » ('j') | chrome/common/extensions/docs/templates/articles/app_lifecycle.html » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

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

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

index 3023a4b22755211abe3db568975b239233fbccf7..9f1f63cc55cf8688d67e31382f13136954f52110 100644

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

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

@@ -2,7 +2,7 @@

<p>

-The <a href="app_architecture.html#security">Chrome Apps security model</a> disallows

+The <a href="app_architecture#security">Chrome Apps security model</a> disallows

external content in iframes and

the use of inline scripting and <code>eval()</code>.

You can override these restrictions,

@@ -27,7 +27,7 @@ Check out the

<h2 id="external">Referencing external resources</h2>

<p>

-The <a href="contentSecurityPolicy.html">Content Security Policy</a> used by apps disallows

+The <a href="contentSecurityPolicy">Content Security Policy</a> used by apps disallows

the use of many kinds of remote URLs, so you can't directly reference external

images, stylesheets, or fonts from an app page. Instead, you can use use

cross-origin XMLHttpRequests to fetch these resources,

@@ -68,7 +68,7 @@ xhr.onload = function(e) {

xhr.send();

</pre>

-<p>You may want to <a href="offline_apps.html#saving-locally">save</a>

+<p>You may want to <a href="offline_apps#saving-locally">save</a>

these resources locally, so that they are available offline.</p>

<h2 id="webview">Embed external web pages</h2>

@@ -97,7 +97,7 @@ Your <code>webview</code> element must include the URL to the source content

and specify its dimensions.

</p>

-<pre data-filename="browser.html">

+<pre data-filename="browser">

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

</pre>

@@ -127,7 +127,7 @@ These pages are then exempt from their Content Security Policy.

Sandboxed pages can use iframes, inline scripting,

and <code>eval()</code>.

Check out the manifest field description for

-<a href="manifest/sandbox.html">sandbox</a>.

+<a href="manifest/sandbox">sandbox</a>.

</p>

<p>

@@ -145,7 +145,7 @@ Here's a sample sandboxed page

which uses an inline script and <code>eval()</code>:

</p>

-<pre data-filename="sandboxed.html">

+<pre data-filename="sandboxed">

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

<html>

<body>

@@ -166,7 +166,7 @@ and list the app pages to be served in a sandbox:

"sandbox": {

- "pages": ["sandboxed.html"]

+ "pages": ["sandboxed"]

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

}

</pre>

@@ -192,7 +192,7 @@ with a window object. However, the sandbox page is created as a new window.

chrome.app.runtime.onLaunched.addListener(function() {

- chrome.app.window.create('window.html', {

+ chrome.app.window.create('window', {

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

'bounds': {

'width': 400,

'height': 400,

@@ -201,7 +201,7 @@ chrome.app.runtime.onLaunched.addListener(function() {

}

});

- chrome.app.window.create('sandboxed.html', {

+ chrome.app.window.create('sandboxed', {

'bounds': {

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

'width': 400,

'height': 400,

@@ -217,7 +217,7 @@ chrome.app.runtime.onLaunched.addListener(function() {

<p>Sandboxed pages can also be embedded within another app page

using an <code>iframe</code>:</p>

-<pre data-filename="window.html">

+<pre data-filename="window">

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

<!DOCTYPE html>

<html>

<head>

@@ -225,7 +225,7 @@ chrome.app.runtime.onLaunched.addListener(function() {

<body>

<p>I am normal app window.</p>

- <iframe src="sandboxed.html" width="300" height="200"></iframe>

+ <iframe src="sandboxed" width="300" height="200"></iframe>

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

</body>

</html>

</pre>

@@ -253,7 +253,7 @@ opens:

var myWin = null;

chrome.app.runtime.onLaunched.addListener(function() {

- chrome.app.window.create('sandboxed.html', {

+ chrome.app.window.create('sandboxed', {

'bounds': {

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

'width': 400,

'height': 400

@@ -288,7 +288,7 @@ Here's a sample message receiver

that gets added to your sandboxed page:

</p>

mkearney1 2014/04/09 19:43:30 Keep .html as it refers to a filename.

-<pre data-filename="sandboxed.html">

+<pre data-filename="sandboxed">

var messageHandler = function(e) {

console.log('Background script says hello.', e.data);

};