Custom handlers should throw SecurityError exception if the URL's origin differs from the document'…

public/web/WebViewClient.h

Index: public/web/WebViewClient.h
diff --git a/public/web/WebViewClient.h b/public/web/WebViewClient.h
index 748a9d3dcfa4027d29bf788bf677378f03322b07..7061e2ff9449091076068c6c9d8588a3bb3eb9d6 100644
--- a/public/web/WebViewClient.h
+++ b/public/web/WebViewClient.h
@@ -261,15 +261,14 @@ public:
 
     // Registers a new URL handler for the given protocol.
     virtual void registerProtocolHandler(const WebString& scheme,
-        const WebURL& baseUrl,
         const WebURL& url,
         const WebString& title) { }
 
     // Unregisters a given URL handler for the given protocol.
-    virtual void unregisterProtocolHandler(const WebString& scheme, const WebURL& baseUrl, const WebURL& url) { }
+    virtual void unregisterProtocolHandler(const WebString& scheme, const WebURL& url) { }
 
     // Check if a given URL handler is registered for the given protocol.
-    virtual WebCustomHandlersState isProtocolHandlerRegistered(const WebString& scheme, const WebURL& baseUrl, const WebURL& url)
+    virtual WebCustomHandlersState isProtocolHandlerRegistered(const WebString& scheme, const WebURL& url)
     {
         return WebCustomHandlersNew;
     }

[abarth-chromium, 2014/08/06 18:34:56]

Is Chromium prepared for this change or will this break these calls?

[pals, 2014/08/06 18:46:47]

This is the chromium side CL
https://codereview.chromium.org/428253006/

[pals, 2014/08/07 14:06:06]

Done.