Strange Behavior about webui HOT 11 CLOSED

No. It turns out that I had an id="webui" attribute and I changed it and boom it worked.

from webui.

Glad to hear that. Also thank you for sharing the screenshot, the SameSite warning is fixed as well (ff97452).

from webui.

Mine is archlinux, using the main branch, everything is normal

from webui.

That's what I would get with the minimal example using the current main branch and using 2.4.2 official archive files after it would be connected for maybe 20-30 seconds. I have used it with zig build and regular gcc as well.

Since I hadn't had issues with the official binaries before now, that made me think it was browser related more compared to webui. Using Firefox 127.0.1 on Arch. Chromium is 126, but that one is on my Mint VM, I mention that, because that's the one picture.

from webui.

The browsers cut the connection if no activity for 2 minutes, so WebUI sends a ping every 20 seconds.

Another issue is sleep mode, OS cut all network activities based on power settings, including WebSocket. This issue gets solved just today (faa02ad) by making WebUI trying to re-connect if backend still alive. More info: #441.

What I suggest is to download the Nightly Build, use debug version instead of release, if issue still exists, then share logs here, and a screenshot of web browser DevTools console logs.

from webui.

I used an application that I was working on, with known working links to open up new windows and file handling and the file handling was not displaying properly, nor would it actually open windows when buttons were pressed. So even if I am wanting to get the server from timing out, it seems to be blocked. Really strange.

log.txt

from webui.

[Core]		_webui_http_handler() -> GET [/webui.js]
[Core]		_webui_http_handler() -> HTTP Status Code: 200
...
[Core]		_webui_server_thread([1]) -> Waiting more for connection
[Core]		_webui_timer_start()
[Loop] webui_wait()
[Loop] webui_wait() -> Waiting (Timeout in 15 seconds)
[Loop] webui_wait() -> Linux web browser loop
[Core]		_webui_server_thread([1]) -> Cleaning
[Core]		_webui_free_port([52942])
[Core]		_webui_free_mem(0x0x7fb4b8000b70)
[Core]		_webui_free_mem(0x0x7fb4b8000b70) -> Free 128 bytes
[Core]		_webui_server_thread([1]) -> Server stopped.
[Loop] webui_wait() -> Cleaning
[Loop] webui_wait() -> Main loop exit successfully

From logs I can say that webui.js is correctly sent, but failed to connect. Can you please share a screenshot of the web browser DevTools console logs?

from webui.

from webui.

from webui.

The error is clearly said that there is another webui object.
More inf:

from webui.

Did you included webui.js twice? or do you have another JavaScript with similar global object name webui?

from webui.