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..e799c54113fd5f757e3d08bd6afb07bd1be2d7f3 100644
--- a/chrome/common/extensions/api/app_runtime.idl
+++ b/chrome/common/extensions/api/app_runtime.idl
@@ -14,10 +14,17 @@ 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.
     DOMString? id;
 
+    // Option 1: the file enries for onLaunched corresponding to a file
+    // handler (file_handlers in the manifest).
     LaunchItem[]? items;
+
+    // Option 2: the URL and referrer's URL for onLaunched corresponding to
+    // a URL handler (url_handlers in the manifest).
+    DOMString? url;
+    DOMString? referrerUrl;

[asargent_no_longer_on_chrome, 2013/08/14 18:05:12]

We might consider wrapping these 2 together into a separate dictionary, e.g.

[inline_doc] dictionary RedirectedUrlData {
  DOMString url;
  DOMString? referrerUrl;  // Null for omnibox navigations, bookmark clicks,
etc.
};

[inline_doc] dictionary LaunchData {
  ...
  RedirectedUrlData? redirect;
  ...
};


That gives a clean separation if we think we might someday want to provide some
additional information, e.g. an enum of "navigation type", etc.

[sergeygs, 2013/08/18 11:40:24]

This would be visible on the external API side, in the signature of onLaunched,
and no objection/suggestion has ever come up in the API reviews about the
proposed signature, so I'm not sure I'm at liberty to do that change.
On 2013/08/14 18:05:12, Antony Sargent wrote:

   };
 
   interface Events {