Remove ScrollableArea::GetFrameViewBase and move ScheduleAnimation into subclasses.

third_party/WebKit/Source/core/frame/FrameView.cpp

Index: third_party/WebKit/Source/core/frame/FrameView.cpp
diff --git a/third_party/WebKit/Source/core/frame/FrameView.cpp b/third_party/WebKit/Source/core/frame/FrameView.cpp
index 75927b342e7ae70614d771402a0ab300b6b05ecf..96039293c40bbf1a261f599596db5e45cd4d7c1b 100644
--- a/third_party/WebKit/Source/core/frame/FrameView.cpp
+++ b/third_party/WebKit/Source/core/frame/FrameView.cpp
@@ -2747,6 +2747,10 @@ void FrameView::ScrollbarStyleChanged() {
   PositionScrollbarLayers();
 }
 
+bool FrameView::ScheduleAnimation() {

[haraken, 2017/04/19 09:44:07]

It seems like we have too many proxy methods to call ScheduleAnimation. Can we
try to remove FrameView::ScheduleAnimation and Frame::ScheduleAnimation?

The caller sites can directly call HostWindow::ScheduleAnimation.

(Not related to this CL, HostWindow should be renamed to PlatformChromeClient.
It's never related to a window.)

[joelhockey, 2017/04/19 10:27:54]

2 CLs on the wey soon for this.

+  return frame_->ScheduleAnimation(GetHostWindow());
+}
+
 void FrameView::NotifyPageThatContentAreaWillPaint() const {
   Page* page = frame_->GetPage();
   if (!page)
@@ -4577,10 +4581,6 @@ bool FrameView::ShouldPlaceVerticalScrollbarOnLeft() const {
   return false;
 }
 
-FrameViewBase* FrameView::GetFrameViewBase() {
-  return this;
-}
-
 LayoutRect FrameView::ScrollIntoView(const LayoutRect& rect_in_content,
                                      const ScrollAlignment& align_x,
                                      const ScrollAlignment& align_y,