Strange behavior with IE9 #180

Closed
gfronza opened this Issue Dec 11, 2012 · 6 comments

3 participants

@gfronza

Hi all,

I'm running Faye Client in different browsers and IE9 came up with a very strange behavior: After a few seconds connected I receive a transport:down. But even after this "disconnection" I'm able to publish in the channel. Other clients connected (using Chrome ou Firefox) receive the messages, but those messages are repeated. This problem is only occurring with IE9 whose selected transport is 'cross-origin-long-polling'.

My server is running in NodeJS and the Faye version is 0.8.6.

Client code:
_client = new Faye.Client(_serverAddr + '/rtc', { timeout: 15, retry: 5 });
BTW: _serverAddr is pointing to a dotcloud instance.

@jcoglan
Collaborator

Would you be able to dig into this? I don't have access to IE9 at the moment. If you can still publish, what should happen is that the transport object should emit up on the successful publish response from the server. Clearly it's spuriously emitting down or failing to emit up when it should.

The source file for this transport is here:
https://github.com/faye/faye/blob/master/javascript/transport/cors.js

@jamesotron jamesotron referenced this issue in jamesotron/faye-rails Feb 5, 2013
Closed

Faye vs IE9 links with href='javascript:' #28

@jcoglan
Collaborator

@gfronza @jamesotron Do either of you have any further insight into this issue?

@jamesotron

I don't sorry, since it's nothing to do with faye-rails. Good luck!

@jcoglan
Collaborator

This sounds like a similar problem to sockjs/sockjs-client#90 -- thanks @jamesotron. Does adding the following line after creating the client in IE fix the problem for you:

client.disable('autodisconnect')

Faye explicitly disconnects the client and its underlying transport on page unload, in order to support garbage collection both on the client and on the server. It could be that the javascript: links are triggering this.

I would advise, if possible, not using javascript: links in the first place since they are a browser misfeature and there are cleaner ways of getting the same behaviour without confusing the browser.

@jcoglan
Collaborator

There's been no response to my last message in six months, can I close this issue?

@gfronza

Yes... I gave up on IE! :)

@gfronza gfronza closed this Aug 28, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment