Fix the JavascriptWindow open CF tests which failed because the pending render view status was not

chrome/browser/automation/automation_resource_message_filter.cc

Index: chrome/browser/automation/automation_resource_message_filter.cc
===================================================================
--- chrome/browser/automation/automation_resource_message_filter.cc	(revision 107827)
+++ chrome/browser/automation/automation_resource_message_filter.cc	(working copy)
@@ -269,7 +269,7 @@
       automation_details_iter->second.filter == filter) {
     DCHECK_GT(automation_details_iter->second.ref_count, 0);
     automation_details_iter->second.ref_count++;
-    // The tab handle may have changed:-
+    // The tab handle and the pending status may have changed:-
     // 1.A external tab container is being destroyed and a new one is being
     //   created.
     // 2.The external tab container being destroyed receives a RVH created
@@ -279,6 +279,7 @@
     // We need to replace the handle of the external tab being destroyed with
     // the new one that is being created."
     automation_details_iter->second.tab_handle = tab_handle;
+    automation_details_iter->second.is_pending_render_view = pending_view;

[robertshield, 2011/10/29 01:02:35]

looking at AutomationDetails, there are two other fields, refcount and filter.
Why is it ok to re-use these from the old instance?

   } else {
     filtered_render_views_.Get()[renderer_key] =
         AutomationDetails(tab_handle, filter, pending_view);