VectorIconButton's main reason for existence is that ImageButton only supports bitmap images. We should add vector image support directly to ImageButton and kill VectorIconButton in favor of that.
Note that VectorIconButton also has some particular behaviors regarding padding sizes, ripples, etc. Most of these should be controlled by the caller. I don't think there are really enough users of this class today to justify an ImageButton subclass that does this stuff. This may require adding a bit more flexibility to ImageButton.
Also note that some of this behavior is undesirable in a Harmony world. For example, hardcoding 4 px of padding around each edge is not really what we want; see https://codereview.chromium.org/2671443002/ . This is another reason why this should probably be specified by the caller, not by the button class.
Marking as a P1 Harmony issue because this seems like the solution for getting e.g. dialog close buttons to match the Harmony spec, so it blocks compliance for all dialogs.
Comment 1 by pkasting@chromium.org
, Feb 27 2017