7.x Work: Delay loading of chat until node.js socket connect established.

There might be a different workaround but depending on the speed of the connections, I've been able to post a message that gets sent to already connected users but not to the user I am connecting as. I guess that means that user isn't connect yet to node.js backend to receive the message, but can send the message out. It would be good to delay loading of chat box until node.js connect established.

This probably relates to a deeper issue about lost connection during a chat. Essentially it's possible to lose a connection but not have any feedback on the client side. Not quite sure of the logic or order of operations on this.