Makes it so that we sync changes in content state more often for selected tabs. This is necesitated by the fact that when closing a tab we don't grab the most recent content state, leaving session restore with slightly stale data. To really fix this requires sending a message on tab close and waiting for it, but that induces tab close jank, something we're not going to do.

BUG=17220
TEST=none

Review URL: http://codereview.chromium.org/342100

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31097 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 2 insertions, 2 deletions

diff --git a/chrome/renderer/render_view_unittest_mac.mm b/chrome/renderer/render_view_unittest_mac.mm
index c2c766f..a83af57 100644
--- a/chrome/renderer/render_view_unittest_mac.mm
+++ b/chrome/renderer/render_view_unittest_mac.mm
@@ -89,7 +89,7 @@ TEST_F(RenderViewTest, MacTestCmdUp) {
 
   // First test when javascript does not eat keypresses -- should scroll.
   sprintf(htmlBuffer, kRawHtml, "true");
-  view_->set_delay_seconds_for_form_state_sync(0);
+  view_->set_send_content_state_immediately(true);
   LoadHTML(htmlBuffer);
   render_thread_.sink().ClearMessages();
 
@@ -112,7 +112,7 @@ TEST_F(RenderViewTest, MacTestCmdUp) {
 
   // Now let javascript eat the key events -- no scrolling should happen
   sprintf(htmlBuffer, kRawHtml, "false");
-  view_->set_delay_seconds_for_form_state_sync(0);
+  view_->set_send_content_state_immediately(true);
   LoadHTML(htmlBuffer);
   render_thread_.sink().ClearMessages();