Fix the absence of padding on some UI buttons.

chrome/browser/ui/views/harmony/layout_delegate.cc

Index: chrome/browser/ui/views/harmony/layout_delegate.cc
diff --git a/chrome/browser/ui/views/harmony/layout_delegate.cc b/chrome/browser/ui/views/harmony/layout_delegate.cc
index d366297d1520fffbeb0db5a3fd029cdd8165bb85..1f80b8776d9492dc62e1618e34ede4c13608d15f 100644
--- a/chrome/browser/ui/views/harmony/layout_delegate.cc
+++ b/chrome/browser/ui/views/harmony/layout_delegate.cc
@@ -23,7 +23,9 @@ LayoutDelegate* LayoutDelegate::Get() {
 int LayoutDelegate::GetMetric(Metric metric) const {
   switch (metric) {
     case Metric::BUTTON_HORIZONTAL_PADDING:
-      return 0;
+      return views::kButtonHorizontalPadding;
+    case Metric::BUTTON_MINIMUM_WIDTH:
+      return views::kMinimumButtonWidth;

[sky, 2017/02/24 04:15:43]

Rather than exposing the constant in views could this call back to a function
exposed on ChromeViewsDelegate to get the value from ViewsDelegate? Said
function could be private and LayoutDelegate a friend.

[Peter Kasting, 2017/02/24 06:32:31]

I don't think we should do that in this patch set, because I think that will be
obsolete in Allen's patch set.  This should be thought of as a stopgap, and his
the patchset that fixes all this at once.

     case Metric::DIALOG_BUTTON_MARGIN:
       return views::kButtonHEdgeMarginNew;
     case Metric::DIALOG_BUTTON_MINIMUM_WIDTH: