Updated docs to explain "intents" section in extension manifest.

chrome/common/extensions/docs/static/manifest.html

 <div id="pageData-name" class="pageData">Formats: Manifest Files</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>
 Every extension, installable web app, and theme has a
 <a href="http://www.json.org">JSON</a>-formatted manifest file,
 named <code>manifest.json</code>,
 that provides important information.
 </p>
 
@@ skipping 37 matching lines @@
 
   "<a href="#nacl_modules">nacl_modules</a>": [...],
   "<a href="#offline_enabled">offline_enabled</a>": true,
   "<a href="omnibox.html">omnibox</a>": { "keyword": "<em>aString</em>" },
   "<a href="options.html">options_page</a>": "<em>aFile</em>.html",
   "<a href="#permissions">permissions</a>": [...],
   "<a href="npapi.html">plugins</a>": [...],
   "<a href="#requirements">requirements</a>": {...},
   "<a href="autoupdate.html">update_url</a>": "http://<em>path/to/updateInfo</em>.xml",
   "<a href="#web_accessible_resources">web_accessible_resources</a>": [...]
+  "<a href="#intents">intents</a>": {...}

[mkearney, 2012/03/09 00:28:50]

These links are in alphabetical order, so you probably want to move this to the
top.

[groby-ooo-7-16, 2012/03/09 20:44:26]

Done.

 }
 </pre>
 
 
 <h2>Field details</h2>
 
 <p>
 This section covers fields that aren't described in another page.
 For a complete list of fields,
 with links to where they're described in detail,
@@ skipping 676 matching lines @@
 </a> 2 or above are <strong>blocked by default</strong>, and must be whitelisted
 for use via this property.
 </p>
 
 <p>
 Resources inside of packages using <code>manifest_version</code> 1 are available
 by default, but <em>if</em> you do set this property, then it will be treated as
 a complete list of all whitelisted resources. Resources not listed will be
 blocked.
 </p>
+
+<h3 id="intents">intents</h3>

[mkearney, 2012/03/09 00:28:50]

These sections are in alphabetical order, so you will want to move this up in
the list accordingly.

[groby-ooo-7-16, 2012/03/09 20:44:26]

Done.

+
+<p>
+A dictionary that specifies all web intents provided by this extension. Each key in the dictionary specifies the action name that is handled by this extent. The following example specifies two handlers for the action "http://webintents.org/share".

[mkearney, 2012/03/09 00:28:50]

What about adding a sentence that briefly defines web intents and links to the
main doc up here rather than later on ? Something like:
Use <a href="http://www.webintents.org">webintents</a>to allow users to control
the services that your extension interacts with. 

[mkearney, 2012/03/09 00:28:50]

'extent' should be 'extension'?

[mkearney, 2012/03/09 00:28:50]

Should this also mention hosted apps?

[groby-ooo-7-16, 2012/03/09 20:44:26]

Done.

[groby-ooo-7-16, 2012/03/09 20:44:26]

webintents are available in packaged apps, hosted apps, and extensions. I use
extension in the generic sense - "This thing described by the manifest". (See
e.g. the way "description" uses the term, too)

I've clarified to "extension or app" in the first usage.

[groby-ooo-7-16, 2012/03/09 20:44:26]

I wish I _had_ a sentence like that. Even webintents.org can't describe them in
a single sentence. Since it's a complex subject, the document assumes basic
knowledge of them. 

Vaguely based this approach on nacl_handlers - that section assumes familiarity
with nacl, but has additional link for an overview at the end.
I changed "web intents" to "intent handlers", to at least clarify what this
section refers to.

On 2012/03/09 00:28:50, mkearney wrote:

[mkearney, 2012/03/09 21:41:15]

Looks good, and yes, I totally know what you mean. I tried all sorts of ways to
narrow the definition down to a sentence or two. Not very doable.

On 2012/03/09 20:44:26, groby wrote:

[mkearney, 2012/03/09 21:41:15]

Can we make "http://webintents.org/share" a link to the share description?

[groby-ooo-7-16, 2012/03/09 22:06:04]

Done.

+</p>
+
+<pre>
+{
+  "name": "test",
+  "version": "1",
+  "intents": {
+    "http://webintents.org/share": [
+      { 
+        "type": ["text/uri-list"],
+        "href": "/services/sharelink.html",
+        "title" : "Sample Link Sharing Intent",
+        "disposition" : "inline"
+      },
+      {
+        "type": ["image/*"],
+        "href": "/services/shareimage.html",
+        "title" : "Sample Image Sharing Intent",
+        "disposition" : "window"
+      }
+    ]
+  }  
+}
+</pre>
+
+<p>
+The value of "type" is an array of mime types that is supported by this handler. "path" indicates the URL of the page that handles the intent. For hosted apps, these URLs must be within the allowed set of URLs. For extensions, all URLs are inside the extension and considered relative to the extension root URL. 

[mkearney, 2012/03/09 00:28:50]

Small - add 'The' before "path".

[groby-ooo-7-16, 2012/03/09 20:44:26]

Done.

+</p>
+
+<p>
+"title" is the handler's title and is displayed in the intent picker UI if the user initiated the action specific to the handler. 
+</p>

[mkearney, 2012/03/09 00:28:50]

Slight rewording:

The "title" is displayed in the intent picker UI when the user initiates the
action specific to the handler.

[groby-ooo-7-16, 2012/03/09 20:44:26]

Done.

+
+<p>
+"disposition" is either "inline" or "window". Intents with "window" disposition will open a new tab when invoked. Intents with "inline" disposition will be displayed inside the intent picker when invoked.

[mkearney, 2012/03/09 00:28:50]

Small - add 'The' before "disposition".

[groby-ooo-7-16, 2012/03/09 20:44:26]

Done.

+</p>
+
+<p>
+For more information on intents, refer to the <a href="dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents specification</a> and <a href="http://www.webintents.org">webintents.org</a>.

[mkearney, 2012/03/09 00:28:50]

If you put the sentence above with the cross-reference to web intents docs, I
think it would be OK to remove this paragraph (making the content a bit
shorter). Also, I don't think you need the specification here, as it is linked
to in the .org doc.

[groby-ooo-7-16, 2012/03/09 20:44:26]

I consider the .org doc to be somewhat in flux (it currently _doesn't_ refer to
the spec :)

Since intents are a brand-new subject, I'd prefer to err on the side of caution
in terms of additional info

We do the same for HTML5 notifications and CSS3D in the "requirements" section.

On 2012/03/09 00:28:50, mkearney wrote:

[mkearney, 2012/03/09 21:41:15]

Sonds good. 

I just tested the link though to the spec, and it appears to be broken.

On 2012/03/09 20:44:26, groby wrote:

[groby-ooo-7-16, 2012/03/09 22:06:04]

That's because it _is_ broken - I forgot the http in front of it :)

On 2012/03/09 21:41:15, mkearney wrote:

+</p>