Plumb the new mixed content API callbacks to the tab contents. We'll actually

use these notifications in a future patch.

No behavior change.

R=agl

Review URL: http://codereview.chromium.org/241004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27249 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 12 insertions, 0 deletions

diff --git a/chrome/renderer/render_view.cc b/chrome/renderer/render_view.cc
index a811503..842dfc0 100644
--- a/chrome/renderer/render_view.cc
+++ b/chrome/renderer/render_view.cc
@@ -130,6 +130,7 @@ using WebKit::WebPopupMenuInfo;
 using WebKit::WebRange;
 using WebKit::WebRect;
 using WebKit::WebScriptSource;
+using WebKit::WebSecurityOrigin;
 using WebKit::WebSettings;
 using WebKit::WebSize;
 using WebKit::WebString;
@@ -2299,6 +2300,17 @@ void RenderView::didLoadResourceFromMemoryCache(
       response.securityInfo()));
 }
 
+void RenderView::didDisplayInsecureContent(WebKit::WebFrame* frame) {
+  Send(new ViewHostMsg_DidDisplayInsecureContent(routing_id_));
+}
+
+void RenderView::didRunInsecureContent(
+    WebFrame* frame, const WebSecurityOrigin& origin) {
+  Send(new ViewHostMsg_DidRunInsecureContent(
+      routing_id_,
+      origin.toString().utf8()));
+}
+
 void RenderView::didExhaustMemoryAvailableForScript(WebFrame* frame) {
   Send(new ViewHostMsg_JSOutOfMemory(routing_id_));
 }