Make chromoting connect always work

remoting/client/extension/background.js

Index: remoting/client/extension/background.js
diff --git a/remoting/client/extension/background.js b/remoting/client/extension/background.js
index b8b400d5c70f90824a5d054e404a980f5a4c137c..1e657773104a05763fd7e1d76f2d824e456c72fa 100644
--- a/remoting/client/extension/background.js
+++ b/remoting/client/extension/background.js
@@ -63,11 +63,26 @@ function openChromotingTab(hostName, hostJid) {
               " hostName='" + request.hostName + "'" +
               " hostJid='" + request.hostJid + "'" +
               " auth_token='" + request.xmppAuth + "'");
-  navigate(newTabUrl, function(tab) {
-      console.log("We're trying now to send to " + tab.id);
-      chrome.tabs.sendRequest(
-          tab.id, request, function() {
-            console.log('Tab finished connect.');
-          });
-    });
+
+  var sendRequestFunc = function (tab) {
+    console.log("We're trying now to send to " + tab.id);

[awong, 2011/02/18 00:31:01]

At some point, I'm wondering if we should have a custom "log" function that
inspects a variable which can be toggled at runtime.

[Alpha Left Google, 2011/02/18 00:44:06]

hm.. i was thinking about this too, but since we don't connect a lot we won't be
writing a lot of of messages so it's ok.

+    chrome.tabs.sendRequest(
+        tab.id, request, function() {
+          console.log('Tab finished connect.');
+        });
+  };
+
+  var checkStatusFunc = function (tab) {
+    if (tab.status == "complete") {
+      sendRequestFunc(tab);
+      return;
+    }
+
+    // Wait for 500ms and then get the tab and check its status.

[awong, 2011/02/18 00:31:01]

Is there no way to have a signal on tab status change?  a 500ms loop is fine as
a stop-gap, but it's guarantees a 500ms latency in the UI.

[Alpha Left Google, 2011/02/18 00:44:06]

there's only two ways, pass arguments as url into chromoting_tab.js, or inspect
the tab status..

There's is a 500ms latency only if the first trial failed, we can shorten the
timeout though.

+    setTimeout(function() {
+        chrome.tabs.get(tab.id, checkStatusFunc);
+      }, 500);
+  }
+
+  navigate(newTabUrl, checkStatusFunc);
 }