Chrome Frame test fixes for Vista/IE7.

chrome_frame/test/data/chrome_frame_tester_helpers.js

 //
 // This script provides some mechanics for testing ChromeFrame
 //
 function onSuccess(name, id) {
   appendStatus("Success reported!");
   onFinished(name, id, "OK");
 }
 
 function onFailure(name, id, status) {
   appendStatus("Failure reported: " + status);
@@ skipping 171 matching lines @@
 
   url += window.location.protocol + "//" + window.location.host;
   if (path.lastIndexOf("/") > 0) {
     url += path.substring(0, path.lastIndexOf("/")) + "/" + pageName;
   } else {
     url += "/" + pageName;
   }
   url += ((queryString == "") ? "" : "?" + queryString);
   return url;
 }
+
+// Write the text for the Chrome Frame ActiveX control into an element.
+// This works around a "feature" of IE versions released between April, 2006
+// and April, 2008 that required the user to click on an ActiveX control to
+// "activate" it.  See http://msdn.microsoft.com/en-us/library/ms537508.aspx.
+function insertControl(elementId, innerHTML) {
+  var e = document.getElementById(elementId);
+  e.innerHTML = innerHTML;

[robertshield, 2011/12/02 22:05:02]

It seems at a glance that there's a fair amount of duplication in the html
passed in here (most of the callers pass most of the same text). Any way the
parts that change could become parameters and the rest moved here to shorten the
test pages?

+}