title: Define transport types on the client side
body: <p>I need to use jsonp-polling for IE, and xhr-polling for Firefox, so I 
  tried to define types of transports on the client side like this: </p>
  
  <pre><code>    if (/Firefox[\/\s](\d+\.\d+)/.test(navigator.userAgent)){ //test for Firefox/x.x or Firefox x.x (ignoring remaining digits); 
              var socket = io.connect(VG.NODE_SERVER_URL,{ 
                      transports:['xhr-polling'] 
              }); 
      } else if (/MSIE (\d+\.\d+);/.test(navigator.userAgent)){ 
              var socket = io.connect(VG.NODE_SERVER_URL,{ 
                      transports:['jsonp-polling'] 
              }); 
      } else { 
              var socket = io.connect(VG.NODE_SERVER_URL); 
      }
  </code></pre>
  
  <p>I tested it on Firefox and added logging on socket.io-client lib. 
  At</p>
  
  <p><a href="https://github.com/LearnBoost/socket.io-client/blob/master/dist/socket.io.js#L1509" rel="noreferrer">https://github.com/LearnBoost/socket.io-client/blob/master/dist/socket.io.js#L1509</a></p>
  
  <p>the option.transports is <code>["xhr-polling", "flashsocket", "htmlfile", 
  "xhr-polling", "jsonp-polling"]</code>, which is right. However, at </p>
  
  <p><a href="https://github.com/LearnBoost/socket.io-client/blob/master/dist/socket.io.js#L1679" rel="noreferrer">https://github.com/LearnBoost/socket.io-client/blob/master/dist/socket.io.js#L1679</a></p>
  
  <p>I do not know why the transports change to <code>["htmlfile", "jsonp- 
  polling", "xhr-polling"]</code>, which has the same sequence as what I 
  defined on server side.</p>
  
  <p>Why doesn't it use the previous option?</p>