Implementation of the "Redirect URLs to Packaged Apps" feature.

chrome/common/extensions/docs/templates/articles/manifest.html

 <h1>Formats: Manifest Files</h1>
 
 
 <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 24 matching lines @@
   "<a href="themes.html">theme</a>": {...},
   "<a href="#app">app</a>": {...},
 
   <em>// Add any of these that you need</em>
   "<a href="event_pages.html">background</a>": {"persistent": false, ...},
   "<a href="background_pages.html">background</a>": {"persistent": true, ...},
   "<a href="override.html">chrome_url_overrides</a>": {...},
   "<a href="content_scripts.html">content_scripts</a>": [...],
   "<a href="../extensions/contentSecurityPolicy.html">content_security_policy</a>": "<em>policyString</em>",
   "<a href="fileBrowserHandler.html">file_browser_handlers</a>": [...],
   "<a href="#file_handlers">file_handlers</a>": {...},

[not at google - send to devlin, 2013/08/30 17:07:58]

you have some epic rebasing to do. This file hasn't looked anything like this
for quite some time.

[sergeygs, 2013/09/02 07:36:22]

Yes, I've been a couple of weeks behind as it turns. Will upload documentation
later in a separate CL.

   "<a href="#homepage_url">homepage_url</a>": "http://<em>path/to/homepage</em>",
   "<a href="#incognito">incognito</a>": "spanning" <em>or</em> "split",
   "<a href="#key">key</a>": "<em>publicKey</em>",
   "<a href="#minimum_chrome_version">minimum_chrome_version</a>": "<em>versionString</em>",
 
   "<a href="#nacl_modules">nacl_modules</a>": [...],
   "<a href="#kiosk_enabled">kiosk_enabled</a>": true,
   "<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="declare_permissions.html">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="#url_handlers">url_handlers</a>": {...},
   "<a href="#web_accessible_resources">web_accessible_resources</a>": [...],
   "<a href="#sandbox">sandbox</a>": [...]
 }
 </pre>
 
 
 <h2 id="field_details">Field details</h2>
 
 <p>
 This section covers fields that aren't described in another page.
@@ skipping 36 matching lines @@
 the browser's extension management UI
 and the <a href="https://chrome.google.com/webstore">Chrome Web Store</a>.
 You can specify locale-specific strings for this field;
 see <a href="i18n.html">Internationalization</a> for details.
 </p>
 
 <h3 id="file_handlers">file_handlers</h3>
 
 <p>
 Used by <a href="../apps/app_lifecycle.html#eventpage">packaged apps</a>
-to specify what types of files the app can handle. An app can have multiple <code>file_handlers</code>, with each one having an identifier, a list of MIME types that can be handled, and
-a title. Here's an example of specifying file handlers:
+to specify what types of files the app can handle. An app can have multiple
+<code>file_handlers</code>, with each one having an identifier, a list of MIME
+types that can be handled, and a title. Here's an example of specifying file handlers:
 </p>
 
 <pre>
 "file_handlers": {
   "text": {
     "types": [
       "text/*"
     ],
     "title": "Text editor"
   },
   "image": {
     "types": [
       "image/png",
       "image/jpeg"
     ],
     "title": "Image editor"
   }
 }
 </pre>
 
 <p>
 To handle files, apps also need to declare the $ref:fileSystem
 permission. Apps can then be passed files in the $ref:app.runtime.onLaunched
 event - either from the system
 file manager (currently supported on ChromeOS only) or by providing
 a path on the <a href="../apps/first_app.html#open">command line</a>.
 </p>
 
+
+<h3 id="url_handlers">url_handlers</h3>
+
+<p>
+Used by <a href="../apps/app_lifecycle.html#eventpage">packaged apps</a>
+to specify what URL patterns the app can handle. An app can have multiple
+<code>url_handlers</code>, with each one having an identifier, a URL pattern
+that can be handled, and a title. Here's an example of specifying URL handlers:
+</p>
+
+<pre>
+"url_handlers": {
+  "presentation": {
+    "matches": [
+      "https://www.foo.com/presentation/view/*",
+      "https://www.bar.com/presentation/view/*"
+    ],
+    "title": "Open presentation"
+  },
+  "spreadsheet_edit": {
+    "matches": [
+      "https://www.foo.com/spreadsheet/edit/*"
+      "https://www.bar.com/spreadsheet/edit/*"
+    ],
+    "title": "Edit spreadsheet"
+  }
+}</pre>
+
+<p>
+Apps can only register to handle URL patterns within domains they can prove
+ownership of, as determined by the <a href="https://chrome.google.com/webstore">Chrome Web Store</a>.
+Apps that do not fulfill this requirement will be rejected by the store.
+This automatically means that at least a complete domain should always be
+specified for all patterns in the <code>matches</code> list. Apps can then be
+passed matching URLs in the $ref:app.runtime.onLaunched event.
+</p>
+
+
 <h3 id="homepage_url">homepage_url</h3>
 
 <p>
 The URL of the homepage for this extension. The extensions management page (chrome://extensions)
 will contain a link to this URL.  This field is particularly useful if you
 <a href="hosting.html">host the extension on your own site</a>. If you distribute your
 extension using the <a href="https://chrome.google.com/webstore">Chrome Web Store</a>,
 the homepage URL defaults to the extension's own page.
 </p>
 
@@ skipping 240 matching lines @@
     "features": ["webgl"]
   }
 }
 </pre>
 
 <p>
 The "plugins" requirement indicates
 if an app or extension requires NPAPI to run.
 This requirement is enabled by default
 when the manifest includes the
-<a href="http://developer.chrome.com/extensions/npapi.html">"plugins" field</a>. 
+<a href="http://developer.chrome.com/extensions/npapi.html">"plugins" field</a>.
 For apps and extensions that still work when plugins aren't available,
 you can disable this requirement
 by setting NPAPI to false.
 You can also enable this requirement manually,
 by setting NPAPI to true,
 as shown in this example:
 </p>
 
 <pre>
 "requirements": {
@@ skipping 207 matching lines @@
 goes into more detail about implementing a sandboxing workflow that enables use
 of libraries that would otherwise have issues executing under extension's
 <a href="../extensions/contentSecurityPolicy.html">default Content Security
 Policy</a>.
 </p>
 
 <p>
 Sandboxed page may only be specified when using
 <a href="#manifest_version"><code>manifest_version</code></a> 2 or above.
 </p>