-
Notifications
You must be signed in to change notification settings - Fork 4
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
Web interface does not work on Win 7 (64 bit) Internet Explorer #62
Comments
Can you send some screenshot displaying what is the problem ? |
Error occurs when trying to run compiled from C function. Message (Win 10, Internet Explorer 11): To compile functions to JS from C we used WebAssembly. According to the documentation, it looks like WebAssembly isn't compatible with Internet Explorer. |
Internet Explorer 11 was released in 2013 , it is now being replaced with Microsoft Edge (on Windows 10). Windows 7 will also lose support soon. I think that we can assume that the user have other browser installed alongside IE. To be kind to users of old OS/browsers we should display information about minimal requirements for the browsers, asking user to open Edge/Chrome or Firefox. See https://caniuse.com/#feat=wasm |
I agree with @grzanka. Other solution is that we could also compile the libamtrack core to pure JS, but it will lower the performance. |
Is it technically possible to use "pure JS" on browser/OS which doesn't support WASM ? |
I guess it is possible, but this solution only give us IE 11, IE lower than 11 have problem with other js functions that we use. I was testing IE 8 and it reported some probles with bundle.js which is produce by react. |
IE 8 was released in 2009, I'd assume it is safe to put in on "unsupported browsers" list |
I've tested also Windows Server 2016 (connecting via Terminal Services to CERN) - it has IE 11 installed and no Edge browser. |
And no Mozilla oraz chorme browser right? |
Nope. It is centrally managed machine, I have no admin rights there. |
But we can support IE11 |
Good idea ! Do we have an issue on that ? |
No description provided.
The text was updated successfully, but these errors were encountered: