Fixes BrowserViewHostedAppTest.Layout when using MD

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

Index: chrome/browser/ui/views/frame/browser_view_layout.cc
diff --git a/chrome/browser/ui/views/frame/browser_view_layout.cc b/chrome/browser/ui/views/frame/browser_view_layout.cc
index a8d1c71940db9671eecdc80bc6967ea6f9f824b6..32204fd42100068dbcb7ccd86bee36a847005d24 100644
--- a/chrome/browser/ui/views/frame/browser_view_layout.cc
+++ b/chrome/browser/ui/views/frame/browser_view_layout.cc
@@ -223,13 +223,13 @@ gfx::Rect BrowserViewLayout::GetFindBarBoundingBox() const {
     // miniature immersive style tab strip is visible. Do not overlap the
     // find bar and the tab strip.
     find_bar_y = top_container_bounds.bottom();
-  } else if (ui::MaterialDesignController::IsModeMaterial()) {
-    find_bar_y = top_container_bounds.bottom() - 6;
   } else {
-    // Position the find bar 1 pixel above the bottom of the top container
-    // so that it occludes the border between the content area and the top
-    // container and looks connected to the top container.
-    find_bar_y = top_container_bounds.bottom() - 1;
+    // Position the find bar above the bottom of the top container so that it
+    // occludes the border between the content area and the top container and
+    // looks connected to the top container.
+    // With Material Design the find bar is pushed a bit higher still.

[tdanderson, 2015/10/09 18:12:09]

nit: I would word this as

"Position the find bar above the bottom of the top container so that it occludes
the border between the content area and the top container. The find bar should
look connected to the top container when material design is not enabled."

[varkha, 2015/10/09 18:20:35]

Done.

+    find_bar_y = top_container_bounds.bottom() -
+                 GetLayoutConstant(FIND_BAR_VERTICAL_OFFSET);
   }
 
   // Grow the height of |bounding_box| by the height of any elements between