Files.app: Fixed the problem that dialog opened by Ctrl+O cannot be expand.

chrome/browser/ui/views/extensions/extension_dialog.cc

Index: chrome/browser/ui/views/extensions/extension_dialog.cc
diff --git a/chrome/browser/ui/views/extensions/extension_dialog.cc b/chrome/browser/ui/views/extensions/extension_dialog.cc
index d8b74ae02e5637027142a2f7bee71ef526967e7d..e830d61d3f098abbfc2eb11fc7badf7ca425aaca 100644
--- a/chrome/browser/ui/views/extensions/extension_dialog.cc
+++ b/chrome/browser/ui/views/extensions/extension_dialog.cc
@@ -57,9 +57,14 @@ ExtensionDialog* ExtensionDialog::Show(
     WebContents* web_contents,
     int width,
     int height,
+    int minWidth,

[sky, 2013/05/08 16:14:42]

min_width, min_height

How do we know we can trust these values? What happens if they are ginormous or
too small?

[hirono, 2013/05/09 02:23:16]

Actually these arguments are added just for calling
NativeViewHost::SetPreferredSize. So how to deal with these values is
depending on each NativeViewHost. Currently ExtensionDialog::Show
is only used from SelectFileDialogExtension and constant values are
passed as these arguments there.

[sky, 2013/05/09 15:51:57]

I was assuming these values are coming from script on a page. If the values
aren't coming from the page then I agree with you.

+    int minHeight,
     const string16& title,
     ExtensionDialogObserver* observer) {
   extensions::ExtensionHost* host = CreateExtensionHost(url, profile);
+  // Preferred size must be set before views::Widget::CreateWindowWithParent
+  // is called because CreateWindowWithParent refers the result of CanResize().
+  host->view()->SetPreferredSize(gfx::Size(minWidth, minHeight));
   if (!host)
     return NULL;
   host->SetAssociatedWebContents(web_contents);