views: Move TopContainerView paint recursion to PaintChildren.

chrome/browser/ui/views/frame/top_container_view.cc

Index: chrome/browser/ui/views/frame/top_container_view.cc
diff --git a/chrome/browser/ui/views/frame/top_container_view.cc b/chrome/browser/ui/views/frame/top_container_view.cc
index e36d6084b0012172d602c20fb2edda4e060454eb..6093ecff24024d60f87f19d84d373daa2cdb96ba 100644
--- a/chrome/browser/ui/views/frame/top_container_view.cc
+++ b/chrome/browser/ui/views/frame/top_container_view.cc
@@ -19,12 +19,14 @@ const char* TopContainerView::GetClassName() const {
   return "TopContainerView";
 }
 
-void TopContainerView::OnPaintBackground(gfx::Canvas* canvas) {
+void TopContainerView::PaintChildren(gfx::Canvas* canvas,
+                                     const views::CullSet& cull_set) {
   if (browser_view_->immersive_mode_controller()->IsRevealed()) {
     // Top-views depend on parts of the frame (themes, window title,
     // window controls) being painted underneath them. Clip rect has already
     // been set to the bounds of this view, so just paint the frame.
     views::View* frame = browser_view_->frame()->GetFrameView();
-    frame->Paint(canvas, views::CullSet());
+    frame->Paint(canvas, cull_set);

[danakj, 2015/03/27 18:50:58]

One question, is it okay to pass thru the same cull_set here? Or would that give
wrong results due to frame not actually being a child? It is still painting by
inspection, but I'm not sure how frame would end up in the cull_set. Is it
somewhere in the tree?

[danakj, 2015/03/27 19:17:26]

I see, the CullSet is empty here. This is due to it being promoted into a layer
out of the aura::Window. When we're in immersivemode the CullSet is not used for
anything in the top controls stuff.

I'm going to change this back to passin an explicitly empty CullSet though
still.

   }
+  View::PaintChildren(canvas, cull_set);
 }