chrome/common/extensions/docs/templates/articles/app_intents.html - Issue 561733004: Fixing path to chrome app samples in documentation

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

Issue 561733004: Fixing path to chrome app samples in documentation (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Adding app.yaml and cron.yaml vesion update Created 6 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/app_identity.html ('k') | chrome/common/extensions/docs/templates/articles/app_network.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

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

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

index 63f12262bdb58028cce280a880c48e8d5881d7df..bf7bc2654937b44ee4838e15f412df562cca4588 100644

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

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

@@ -15,14 +15,14 @@ such as editing images via the <code>manifest.json</code>;

your application can also invoke actions to be handled by other applications.

</p>

-<p>Chrome Apps use Web Intents as their primary mechanism for inter-app

+<p>Chrome Apps use Web Intents as their primary mechanism for inter-app

communication.</p>

<b>API Samples: </b>

Want to play with the code?

Check out the

-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/webintents">webintents</a> sample.

+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/webintents">webintents</a> sample.

</p>

<h2 id="register">Register your app to handle an action</h2>

@@ -47,10 +47,10 @@ You must supply the intent in the manifest:

</pre>

<p>

-Unlike extensions and hosted apps, Chrome applications do not

-need a "href" attribute in the manifest declaration, this is

-because Chrome Apps have a single entry point for

-launch - the <code>onLaunched</code> event.

+Unlike extensions and hosted apps, Chrome applications do not

+need a "href" attribute in the manifest declaration, this is

+because Chrome Apps have a single entry point for

+launch - the <code>onLaunched</code> event.

</p>

<h2 id="content">Handling content types</h2>

@@ -67,7 +67,7 @@ For example, your application could handle viewing images or viewing pdfs.

You must supply the intent in the manifest

and use the "http://webintents.org/view" action:

</p>

-<p>To be able declare your application's ability to view RSS and ATOM

+<p>To be able declare your application's ability to view RSS and ATOM

feeds, you would add the following to your manifest.

</p>

@@ -111,7 +111,7 @@ chrome.exe --app-id [app_id] [path_to_file]

</pre>

<p>

This will implicity launch your application with an intent payload populated

-with the action set to "http://webintents.org/view", the type set to the

+with the action set to "http://webintents.org/view", the type set to the

mime-type of the file and the data as a <code>FileEntry</code> object.

</p>

<pre>