Introduce WebKit::WebSecurityOrigin as a wrapper around

WebCore::SecurityOrigin.

This provides us a little wiggle room in the future in
case we ever want to provide more details about a
security origin beyond just its stringified value.
This was done on recommendation from Adam Barth.

R=jorlow
BUG=21967
TEST=none

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

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

1 files changed, 2 insertions, 1 deletions

diff --git a/webkit/tools/test_shell/test_webview_delegate.cc b/webkit/tools/test_shell/test_webview_delegate.cc
index 903e3d2..e8346dc 100644
--- a/webkit/tools/test_shell/test_webview_delegate.cc
+++ b/webkit/tools/test_shell/test_webview_delegate.cc
@@ -83,6 +83,7 @@ using WebKit::WebPopupMenu;
 using WebKit::WebRange;
 using WebKit::WebRect;
 using WebKit::WebScreenInfo;
+using WebKit::WebSecurityOrigin;
 using WebKit::WebSize;
 using WebKit::WebString;
 using WebKit::WebTextAffinity;
@@ -930,7 +931,7 @@ void TestWebViewDelegate::didDisplayInsecureContent(WebFrame* frame) {
 }
 
 void TestWebViewDelegate::didRunInsecureContent(
-    WebFrame* frame, const WebString& security_origin) {
+    WebFrame* frame, const WebSecurityOrigin& origin) {
   if (shell_->ShouldDumpFrameLoadCallbacks())
     printf("didRunInsecureContent\n");
 }