Make canNavigate() OOPI-friendly

Source/core/frame/Frame.h

Index: Source/core/frame/Frame.h
diff --git a/Source/core/frame/Frame.h b/Source/core/frame/Frame.h
index 8c72c8b18225e980ecaa909b9cce10f2bd158000..97d33fe0b1bddd9765dd542bbfd4bc580724211d 100644
--- a/Source/core/frame/Frame.h
+++ b/Source/core/frame/Frame.h
@@ -86,6 +86,11 @@ public:
 
     virtual SecurityContext* securityContext() const = 0;
 
+    Frame* findFrameForNavigation(const AtomicString& name, Frame* activeFrame);
+
+    bool canNavigate(const Frame&);
+    virtual void printNavigationErrorMessage(const Frame&, const char* reason) { }

[dcheng, 2014/12/13 01:55:48]

Perhaps keep this pure virtual for consistency? There should only be two Frame
implementations, so it shouldn't be too big of a cost.

[Nate Chapin, 2014/12/20 00:09:14]

Done.

+
     RenderPart* ownerRenderer() const; // Renderer for the element that contains this frame.
 
     // FIXME: These should move to RemoteFrame when that is instantiated.