Don't transition to in-session mode until the connection has been established.

remoting/webapp/me2mom/client_session.js

Index: remoting/webapp/me2mom/client_session.js
diff --git a/remoting/webapp/me2mom/client_session.js b/remoting/webapp/me2mom/client_session.js
index 553b423aa1b7a9ec669d7976dec1c9a25363da8b..4d332129b9106de1387a5b0d4d3e129148861815 100644
--- a/remoting/webapp/me2mom/client_session.js
+++ b/remoting/webapp/me2mom/client_session.js
@@ -111,6 +111,8 @@ remoting.ClientSession.prototype.createPluginAndConnect =
   this.plugin.id = this.PLUGIN_ID;
   this.plugin.src = 'about://none';
   this.plugin.type = 'pepper-application/x-chromoting';
+  this.plugin.width = 0;
+  this.plugin.height = 0;

[Jamie, 2011/07/25 23:09:50]

Although the plugin is blank until we transition to a new state, this feels like
the correct behaviour.

   container.appendChild(this.plugin);
 
   if (!this.isPluginVersionSupported_(this.plugin)) {
@@ -320,10 +322,10 @@ remoting.ClientSession.prototype.connectionInfoUpdateCallback = function() {
  * @return {void} Nothing.
  */
 remoting.ClientSession.prototype.setState_ = function(state) {
-  this.state = state;
   if (this.onStateChange) {
-    this.onStateChange(this.state);
+    this.onStateChange(state);
   }
+  this.state = state;

[Jamie, 2011/07/25 23:09:50]

Defer setting the current state so that the callback can examine it.

[awong, 2011/07/26 18:51:27]

Huh...We should document clearly that onStateChange is a "pre-change" event. 
Normally, I code things post-change, but as long as we're consistent and clear
about the synchronization, either method works.

[Jamie, 2011/07/26 19:02:35]

Yes, that's generally my preference too, but if the callbacks needs both the
before and after states, pre-change makes more sense. I've added a comment.

 };
 
 /**