Plumbing for frame-specific WebWidgets

Source/core/page/Chrome.h

Index: Source/core/page/Chrome.h
diff --git a/Source/core/page/Chrome.h b/Source/core/page/Chrome.h
index 13ec07a4dd9a7528d95b2a95110f9f08096bf785..2b7f8f870ce337f16402852a6841843d3bfcadb8 100644
--- a/Source/core/page/Chrome.h
+++ b/Source/core/page/Chrome.h
@@ -68,6 +68,8 @@ public:
 
     virtual void scheduleAnimation() override;
 
+    void scheduleAnimationForFrame(LocalFrame* rootFrame);

[dcheng, 2014/11/24 22:30:39]

How come this doesn't need to be a virtual on HostWindow like
scheduleAnimation()? Are we going to get rid of the no-argument version in the
long run? It seems like it'd be easier if we didn't have to sometimes work with
WebView and sometimes with WebFrame.

[kenrb, 2014/11/25 17:14:56]

For WebView vs WebFrame, the goal is to strip most of this code out of WebView
as soon as we are able to use a WebFrameWidget on the top-level frame.

I don't know yet what needs to be done with HostWindow. We will have to revisit
this code later, in any case.

+
     void contentsSizeChanged(LocalFrame*, const IntSize&) const;
 
     void setCursor(const Cursor&);