Change check for WebSocket existence

Safari identifies its WebSocket as "object", whereas Chrome is
"function". By switching our check, we're forcing Chrome to use
long polling. This cheats us around the Chrome-14 issue, while
enabling WebSockets for Safari.

javascripts/chloe-websocket.js

@@ -36,5 +36,5 @@ Chloe.WebSocketTransport.prototype = {
 };
 
 Chloe.WebSocketTransport.isEnabled = function () {
-  return typeof(WebSocket) === "function";
+  return typeof(WebSocket) === "object";
 };