Add VectorIconButton functionality to ImageButton.

ui/views/animation/ink_drop_host_view.cc

Index: ui/views/animation/ink_drop_host_view.cc
diff --git a/ui/views/animation/ink_drop_host_view.cc b/ui/views/animation/ink_drop_host_view.cc
index 85e62b88d93e8c24f9b4d3efb13a25dc2a5336bd..fb286eb97b6bf5436a4cb873f55d657cbf24da2d 100644
--- a/ui/views/animation/ink_drop_host_view.cc
+++ b/ui/views/animation/ink_drop_host_view.cc
@@ -166,8 +166,8 @@ std::unique_ptr<InkDropHighlight> InkDropHostView::CreateInkDropHighlight()
 }
 
 std::unique_ptr<InkDropRipple> InkDropHostView::CreateDefaultInkDropRipple(
-    const gfx::Point& center_point,
-    const gfx::Size& size) const {
+    const gfx::Point& center_point) const {
+  const gfx::Size& size = GetInkDropSize();
   std::unique_ptr<InkDropRipple> ripple(new SquareInkDropRipple(
       CalculateLargeInkDropSize(size), kInkDropLargeCornerRadius, size,
       kInkDropSmallCornerRadius, center_point, GetInkDropBaseColor(),
@@ -176,8 +176,9 @@ std::unique_ptr<InkDropRipple> InkDropHostView::CreateDefaultInkDropRipple(
 }
 
 std::unique_ptr<InkDropHighlight>
-InkDropHostView::CreateDefaultInkDropHighlight(const gfx::PointF& center_point,
-                                               const gfx::Size& size) const {
+InkDropHostView::CreateDefaultInkDropHighlight(
+    const gfx::PointF& center_point) const {
+  const gfx::Size& size = GetInkDropSize();
   std::unique_ptr<InkDropHighlight> highlight(new InkDropHighlight(
       size, kInkDropSmallCornerRadius, center_point, GetInkDropBaseColor()));
   highlight->set_explode_size(CalculateLargeInkDropSize(size));
@@ -296,4 +297,9 @@ InkDropHostView::CreateDefaultFloodFillInkDropImpl() {
   return ink_drop;
 }
 
+gfx::Size InkDropHostView::GetInkDropSize() const {
+  return gfx::Size(std::min(size().width(), kDefaultInkDropSize),

[bruthig, 2017/03/09 05:04:42]

|kDefaultInkDropSize| is somewhat of an arbitrary value and I've been wanting to
remove it for a while.  I feel like this change is only making more engrained. 
Can you extend ImageButton with a new FindInPageButton that overrides
CreateInkDropRipple() and CreateInkDropHighlight() to return the right sized
effects and remove the changes to InkDropHostView?

I think that the Button refactor that I have planned will eventually purge this
FindInPageButton.

[Bret, 2017/03/09 22:32:37]

It's not just the find-in-page buttons, I modified those because they had a
layout problem when we changed their size for Harmony. Here I'm trying to make
sure the ink drop sizes are reasonable when the button is smaller than 24dip. I
don't like the default constant either but I don't see how this is making it
more ingrained; all buttons are relying on it either way.

[bruthig, 2017/03/10 14:35:25]

I guess I dislike the conditional 'min()' logic more than the constant itself.
Prior to your change it was possible to statically determine what ink drop size
was being used on a button.  With this conditional change I'm now going to need
to know the run time size of the button.  This is going to make it harder to
perform the button refactor and extract the ink drop as an effect.  I will have
to either reverse engineer the run time sizes or I'm going to have to dig up all
of the designer specs.

As a compromise, I'd be happy with introducing an
InkDropHostView::SetDefaultInkDropSize() that clients can use instead if needed.
 This would at least white-list the buttons that require the behavior.

+                   std::min(size().height(), kDefaultInkDropSize));
+}
+
 }  // namespace views