Adds navigator.registerProtocolHandler.

chrome/browser/tab_contents/tab_contents.cc

Index: chrome/browser/tab_contents/tab_contents.cc
diff --git a/chrome/browser/tab_contents/tab_contents.cc b/chrome/browser/tab_contents/tab_contents.cc
index 2f946be16bb945a3a29a5caff2461bab3e7b1847..34d5adfab950d0053758e08c3dcecf0b08436728 100644
--- a/chrome/browser/tab_contents/tab_contents.cc
+++ b/chrome/browser/tab_contents/tab_contents.cc
@@ -22,6 +22,8 @@
 #include "chrome/browser/child_process_security_policy.h"
 #include "chrome/browser/content_settings/content_settings_details.h"
 #include "chrome/browser/content_settings/host_content_settings_map.h"
+#include "chrome/browser/custom_handlers/protocol_handler_registry.h"
+#include "chrome/browser/custom_handlers/register_protocol_handler_infobar_delegate.h"
 #include "chrome/browser/debugger/devtools_manager.h"
 #include "chrome/browser/defaults.h"
 #include "chrome/browser/desktop_notification_handler.h"
@@ -2620,6 +2622,23 @@ void TabContents::ProcessExternalHostMessage(const std::string& message,
     delegate()->ForwardMessageToExternalHost(message, origin, target);
 }
 
+void TabContents::RegisterProtocolHandler(const std::string& protocol,
+                                          const GURL& url,
+                                          const string16& title) {
+  ProtocolHandler* handler = ProtocolHandler::CreateProtocolHandler(protocol, url, title);
+
+  if (handler == NULL) {
+    return;
+  }
+
+  if (profile()->GetProtocolHandlerRegistry()->IsAlreadyRegistered(handler)) {
+      return;

[tony, 2011/02/14 23:40:07]

Nit: 2 space indent.  I would probably add a TODO(koz) about replacing existing
handlers.

[koz (OOO until 15th September), 2011/02/15 03:37:27]

Actually I've implemented the logic for showing a different message when we are
replacing a protocol handler - it's in
register_protocol_handler_infobar_delegate.cc. This line is so that if the site
tries to register an identical protocol handler to one that's already registered
then we don't bother the user with it and drop the request.

Actually, we probably want to at least notify the user of that. FireFox does
that, and if a site presents a link or button to let the user register a
protocol handler, then having no feedback for it in some cases would be
confusing.

I'll add that in this patch (it should only be one line here).

+  }
+
+  AddInfoBar(new RegisterProtocolHandlerInfoBarDelegate(
+      this, profile()->GetProtocolHandlerRegistry(), handler));
+}
+
 void TabContents::RunJavaScriptMessage(
     const std::wstring& message,
     const std::wstring& default_prompt,