-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client-Library not working with IE8/9 #154
Comments
According to the table "Supported transports, by browser" at https://github.com/sockjs/sockjs-client it seems like SockJS is trying transports in the intended order for IE8/9 (i.e. iframe-htmlfile first and iframe-xhr-polling second when cookie_needed is true). However, for some reason both these transports fail, and the connection is unsuccessful. |
I think this is an additional problem. My problem is that IE8 don't even parse the client-library |
(I just haven't redeployed the example yet with the latest version) |
You are too fast for me. Thanks in advance! |
Gonna close this as the original issue of this topic has been solved. |
I'm getting errors, but don't know why at the moment. Maybe related with this topic. First I did: When emulation IE8 (in IE10) with this server: npm install git+https://github.com/primus/primus.git primus = new Primus(server, { the client code: Then it works in ie10/chrome/firefox/safari readyStateChange But gives me no error, (or ie don't give me the error) because i'm using: .on('error', function(e){ edit: |
Hi,
Im using Primus 1.5.1 at the moment.
I tested with IE10, IE9 and IE8. Each of them got Javascript errors in the primus-client-library.
Example: open http://primus-example.nodejitsu.com/ with IE8, 9
It only works for me with IE10/11.
I plan to use primus in production for an additional websocket-based service.
I used sockjs before which supported IE from IE6 onward, but decided to switch to primus to switch transformers if i must.
About 15% of my Users use IE8/9 so this is actually a showstopper for me.
I didn't find any minimal Browser requirements for primus in the documentation.
Is IE>=10 intentional, or could this be changed to supoort at least IE8 onwards ?
Regards
Andy
The text was updated successfully, but these errors were encountered: