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

chrome/common/extensions/api/app_runtime.idl

Index: chrome/common/extensions/api/app_runtime.idl
diff --git a/chrome/common/extensions/api/app_runtime.idl b/chrome/common/extensions/api/app_runtime.idl
index 391adaa80b9393334939fb27f8af9ef7c0529b68..c3e3765a61df543b213d9d89303b2c9fda48f562 100644
--- a/chrome/common/extensions/api/app_runtime.idl
+++ b/chrome/common/extensions/api/app_runtime.idl
@@ -14,10 +14,22 @@ namespace app.runtime {
 
   // Optional data for the launch.
   [inline_doc] dictionary LaunchData {
-    // The id of the file handler that the app is being invoked with.
+    // The ID of the file or URL handler that the app is being invoked with.
+    // Handler IDs are the top-level keys in the 'file_handlers' and/or
+    // 'url_handlers' dictionaries in the manifest.

[not at google - send to devlin, 2013/08/29 17:35:56]

for all instance of 'foo' change to <code>foo</code>.

even better: link to where they are documented with <code><a
href="file_handlers.html">file_handlers</a></code> etc. you will need to add
docs for url handlers eventually, so remember to link to those.

[sergeygs, 2013/08/30 00:39:44]

Done (the first option). I think docs for url_handlers will not have their own
separate html, just like most manifest keys, including file_handlers. Most of
them just have a section in manifest.html. I'll see if I can add references to
there.

     DOMString? id;
 
+    // The file entries for onLaunched corresponding to a file handler
+    // from the 'file_handlers' key in the manifest.
     LaunchItem[]? items;
+
+    // The URL for onLaunched corresponding to a URL handler from the
+    // 'url_handlers' key in the manifest.
+    DOMString? url;
+
+    // The referrer URL for onLaunched corresponding to a URL handler
+    // from the 'url_handlers' key in the manifest.
+    DOMString? referrerUrl;
   };
 
   interface Events {