views: implement width snapping for DialogDelegateViews

chrome/browser/ui/views/create_application_shortcut_view.cc

Index: chrome/browser/ui/views/create_application_shortcut_view.cc
diff --git a/chrome/browser/ui/views/create_application_shortcut_view.cc b/chrome/browser/ui/views/create_application_shortcut_view.cc
index a8f215ca53ecf98b42e1dcfc209bb88d67a84656..9eb4d1b72f81bc0fa0a13d6d2880c92015e2dd53 100644
--- a/chrome/browser/ui/views/create_application_shortcut_view.cc
+++ b/chrome/browser/ui/views/create_application_shortcut_view.cc
@@ -320,7 +320,7 @@ void CreateApplicationShortcutView::InitControls(DialogLayout dialog_layout) {
   }
 }
 
-gfx::Size CreateApplicationShortcutView::GetPreferredSize() const {
+gfx::Size CreateApplicationShortcutView::GetUnsnappedPreferredSize() const {
   // TODO(evanm): should this use IDS_CREATE_SHORTCUTS_DIALOG_WIDTH_CHARS?

[Peter Kasting, 2017/03/30 00:35:34]

Yes, or that should be removed, because it's unused currently.

But really this is another case where we should be computing the unsnapped width
in a more granular way.  There's no tracking bug in the spreadsheet for
Create[Url,Chrome]ApplicationShortcutView (which is this is parent of); I'd file
one, add it to the sheet, then add a note in that bug about this and a TODO here
referencing the bug.

   static const int kDialogWidth = 360;
   int height = GetLayoutManager()->GetPreferredHeightForWidth(this,