Skip to content
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

conStatus doesn't update on Apple OSs #238

Open
mc-hamster opened this issue Jun 4, 2023 · 3 comments
Open

conStatus doesn't update on Apple OSs #238

mc-hamster opened this issue Jun 4, 2023 · 3 comments

Comments

@mc-hamster
Copy link

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:

  • Use Safari or Chrome on latest iOS or MAC OS.
  • Open a page that is rendered with ESPUI.
  • Disconnect from your WIFI

This works as expected on Android.

Expected behavior
I would expect that the message changes from "Connected" to "Error / No Connection".

Screenshots
image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

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.

@s00500
Copy link
Owner

s00500 commented Oct 6, 2023

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..

@MartinMueller2003
Copy link
Collaborator

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.

@MartinMueller2003
Copy link
Collaborator

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants