Make ARC's intent picker use the buttons insets.

chrome/browser/ui/views/intent_picker_bubble_view.cc

Index: chrome/browser/ui/views/intent_picker_bubble_view.cc
diff --git a/chrome/browser/ui/views/intent_picker_bubble_view.cc b/chrome/browser/ui/views/intent_picker_bubble_view.cc
index 9632fbf6327da47678aaf2cedd7f037f5c05542f..e349f9415d20a4fabf5891414f2149a40250f6b6 100644
--- a/chrome/browser/ui/views/intent_picker_bubble_view.cc
+++ b/chrome/browser/ui/views/intent_picker_bubble_view.cc
@@ -110,6 +110,7 @@ void IntentPickerBubbleView::ShowBubble(
       views::BubbleDialogDelegateView::CreateBubble(delegate);
   delegate->GetDialogClientView()->set_button_row_insets(

[sky, 2017/05/10 15:27:02]

Can this be moved above line 109 such that 113 is not necessary? Otherwise I
think set_button_row_insets sure become SetButtonRowInsets() and it should force
a layout. In other words you shouldn't have to manually call
UpdateDialogButtons.

[djacobo, 2017/05/10 18:14:20]

I don't think that's possible since CreateBubble calls Init, so before that
everything GetDialogClientView is still not constructed, right? I did the
suggested experiment and the Browser crashes while trying to start the picker.

       gfx::Insets(kDialogDelegateInsets));
+  delegate->GetDialogClientView()->UpdateDialogButtons();
 
   delegate->SetArrowPaintType(views::BubbleBorder::PAINT_NONE);
   delegate->SetAlignment(views::BubbleBorder::ALIGN_EDGE_TO_ANCHOR_EDGE);