You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hm... @MartinMueller2003 you have improved this code already once, any idea ? else I can maybe take a quick look at it when back home some time next week..
Since it works on Android and not on iOS it sounds like a browser issue. I can take a look if anything "non-standard" is being done in the Java Script, but everything I saw looked pretty generic.
Yes you can assign this to me. I dont have the ability to modify any of the ticket fields.
@mc-hamster
The key seems to be in how WebSocket.error is handled. Can you open the browser console and see if you get one of these two messages after the WiFi is disconnected:
websock close
websock Error
If neither message is coming out then the websocket layer is failing to report the loss of connection. How long did you wait after the WiFi went down?
Describe the bug
The conStatus stays "Connected" on iOS browsers and MAC OS browsers -- tested on both Safari and Chrome.
To Reproduce
Steps to reproduce the behavior:
This works as expected on Android.
Expected behavior
I would expect that the message changes from "Connected" to "Error / No Connection".
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Device: MacBook Pro
OS: 13.3.1 (a)
Browser Safari 16.4 & Chrome 113.0.5672.126
Device: iPhone
OS: 16.4.1
Browser Safari
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: