Adds navigator.registerProtocolHandler.

chrome/browser/renderer_host/render_view_host.cc

Index: chrome/browser/renderer_host/render_view_host.cc
diff --git a/chrome/browser/renderer_host/render_view_host.cc b/chrome/browser/renderer_host/render_view_host.cc
index dd2dd5d05c8ff88b9655135822b64ac303b0ce74..5af5e8e58538560157d2f51d3fe9b1d617cc0392 100644
--- a/chrome/browser/renderer_host/render_view_host.cc
+++ b/chrome/browser/renderer_host/render_view_host.cc
@@ -769,6 +769,8 @@ bool RenderViewHost::OnMessageReceived(const IPC::Message& msg) {
     IPC_MESSAGE_HANDLER(ViewHostMsg_ForwardMessageToExternalHost,
                         OnMsgForwardMessageToExternalHost)
     IPC_MESSAGE_HANDLER(ViewHostMsg_SetTooltipText, OnMsgSetTooltipText)
+    IPC_MESSAGE_HANDLER(ViewHostMsg_RegisterProtocolHandler,
+                        OnMsgRegisterProtocolHandler)
     IPC_MESSAGE_HANDLER_DELAY_REPLY(ViewHostMsg_RunJavaScriptMessage,
                                     OnMsgRunJavaScriptMessage)
     IPC_MESSAGE_HANDLER_DELAY_REPLY(ViewHostMsg_RunBeforeUnloadConfirm,
@@ -1219,6 +1221,12 @@ void RenderViewHost::OnMsgSelectionChanged(const std::string& text) {
     view()->SelectionChanged(text);
 }
 
+void RenderViewHost::OnMsgRegisterProtocolHandler(const std::string& protocol,
+                                                  const GURL& url,
+                                                  const string16& title) {
+  delegate_->RegisterProtocolHandler(protocol, url, title);

[jam, 2011/02/15 18:48:39]

there's no point in dispatching the message just to call a function in
TabContents through the RenderViewHostDelegate interface.  Just dispatch the
message in TabContents directly

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

Done.

+}
+
 void RenderViewHost::OnMsgRunJavaScriptMessage(
     const std::wstring& message,
     const std::wstring& default_prompt,