Reenable framebusting

third_party/WebKit/Source/core/frame/LocalFrame.h

Index: third_party/WebKit/Source/core/frame/LocalFrame.h
diff --git a/third_party/WebKit/Source/core/frame/LocalFrame.h b/third_party/WebKit/Source/core/frame/LocalFrame.h
index da62177aeabab49db8943344be18308a28f0f0c6..c19a379eb8c5fba0de9a41d414a312385166b07b 100644
--- a/third_party/WebKit/Source/core/frame/LocalFrame.h
+++ b/third_party/WebKit/Source/core/frame/LocalFrame.h
@@ -123,6 +123,8 @@ class CORE_EXPORT LocalFrame final : public Frame,
   void didChangeVisibilityState() override;
   void setDocumentHasReceivedUserGesture() override;
 
+  bool hasReceivedUserGesture() const { return m_hasReceivedUserGesture; }
+
   void detachChildren();
   void documentAttached();
 
@@ -269,6 +271,7 @@ class CORE_EXPORT LocalFrame final : public Frame,
   float m_textZoomFactor;
 
   bool m_inViewSourceMode;
+  bool m_hasReceivedUserGesture;

[Nate Chapin, 2017/01/11 19:01:40]

This won't propagate if this frame goes cross-process. I don't know how much of
a problem that is in practice, but it does mean their would be a behavior
difference between site isolation enabled and disabled.

[ojan, 2017/01/11 19:15:48]

I think we need to come up with a solution that is unaffected by site isolation.
Unfortunately, I can't think of anything other than just making this work
properly across processes. 

Also, is there a test for showing that you can navigate the top-level page after
the frame has been navigated?

 
   Member<InstrumentingAgents> m_instrumentingAgents;
   Member<PerformanceMonitor> m_performanceMonitor;