chromeos: Fix closing issues with WebUI form-repost dialog.

chrome/browser/repost_form_warning_uitest.cc

Index: chrome/browser/repost_form_warning_uitest.cc
diff --git a/chrome/browser/repost_form_warning_uitest.cc b/chrome/browser/repost_form_warning_uitest.cc
index 7a60459713c3f807bd67c9ab9a28499b7d85a902..8b18cde5015e109180e72a3ebe2727ef4949b9f9 100644
--- a/chrome/browser/repost_form_warning_uitest.cc
+++ b/chrome/browser/repost_form_warning_uitest.cc
@@ -48,8 +48,17 @@ TEST_F(RepostFormWarningTest, MAYBE_TestDoubleReload) {
   tab->ReloadAsync();
   tab->ReloadAsync();
 
+  // There should only be one dialog open.
+  int num_constrained_windows = 0;
+  ASSERT_TRUE(tab->GetConstrainedWindowCount(&num_constrained_windows));

[Daniel Erat, 2011/12/01 23:44:49]

Do you happen to know if it's safe to check this immediately after the
ReloadAsync() calls, or is there a risk that the dialog won't be shown yet?

[Bernhard Bauer, 2011/12/01 23:54:53]

No, it should appear immediately. The async in there just means that we don't
wait for the navigation to complete (as we will show the dialog instead of
navigating).

+  EXPECT_EQ(1, num_constrained_windows);
+
   // Navigate away from the page (this is when the test usually crashes).
   ASSERT_TRUE(tab->NavigateToURL(test_server.GetURL("bar")));
+
+  // The dialog should've been closed.
+  ASSERT_TRUE(tab->GetConstrainedWindowCount(&num_constrained_windows));
+  EXPECT_EQ(0, num_constrained_windows);
 }
 
 #if defined(OS_WIN)