-
-
Notifications
You must be signed in to change notification settings - Fork 572
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
Safari iPhone - A problem occurred with this webpage so it was reloaded #487
Comments
Not sure if I will be able to test it, I have access to BrowserStack and I can test iPhone, there are few option that I can test to run local node.js in BrowserStack. Will try to check if on this setup the library is also broken. |
Thanks @jcubic for taking care.
|
Sorry but this project is not maintained see hallard/WebSocketToSerial#2 it will be hard to debug someone else old library. Last commit was year ago. How can I be sure that this project even work for your case. And what is ESP8266 device? |
Hi, indeed, the project I use is abandoned, It is up to you to close the ticket or dig a bit more. No problem. Regardless of ESP8266 specific of the project, the test web page emulation link https://github.com/hallard/WebSocketToSerial#test-web-page-without-esp8266 uses your terminal w/o ESP device, just by a node "server" instead. PC + chrome and Mozilla work fine on it, while iPhone' Safari doesn't. When I use a simple ws test page above in the phone instead, then it works again. That's it, It could be wrong implementation or so ... just reporting. |
This is really broken project, not package.json for node and server give errors when running
and running from link give HTTPS Cors errors: https://cdn.rawgit.com/hallard/WebSocketToSerial/master/webdev/index.htm |
You need to create better example that I can test, some public web socket server will be best, that will not give errors, that is broken when using with terminal on iPhone/Safari. This project is just some garbage, and it use terminal from 2016. |
Can you write maybe code that use jQuery Terminal latest version like the one your provided here and use web sockets that is crashing. That would be helpful and will not close such issue even if I can't test it. But probably will be if the websockets is public like with some service that give free node.js hosting like https://glitch.com/ |
Hi, the issue was caused by usage of jQuery(document).ready at the index.htm of this old project. iOS / Safari has problem with it. Obviously I need to learn more of your examples and do it from scratch. |
So this is solved, right? as for jQuery on ready try using shortcut |
Yes, I will try to change terminal's html to use $(function() {}) instead of .ready. You can close the ticket. The project there is obsolete and I will do the whole thing differently for my needs, including the server side websocket on ESP8266 cheap IoT device - it has already a good library. If you are curious, here is the best short guide: https://tttapa.github.io/ESP8266/Chap14%20-%20WebSocket.html |
Expected behavior
To work
Actual behavior
On Safari Browser, the page reloads and "A problem occurred with this webpage so it was reloaded" warning is shown on each attempt to send "help" or "connect" by the enter button of iphone virtual keyboard
Steps to reproduce
Use nodejs as described as server side and iPhone on same network to act as a client browser (Safari)
https://github.com/hallard/WebSocketToSerial#test-web-page-without-esp8266
You need to update the js and css to latest terminal versions otherwise on ios it will not even show the keyboard. Also on nodejs modules and code use mime-types instead of mime
Same behavior is on a real device .
Browser and OS
Safari ios 12.2 Iphone 6
This nice jquery teminal works fine on above project when connecting with PC and various browsers. except on latest Safari on iPhone. Tried with old and new releases of your code. Suspecting something related to insecure http because another browser (Azul) app. works fine on same phone.
On the other side, the Safari works fine on your demo online terminal (https)
The text was updated successfully, but these errors were encountered: