this post was submitted on 04 Jul 2023
1 points (100.0% liked)

hexbear

10243 readers
31 users here now

Now that the old Hexbear fork has been officially abandoned, this community will be used as a space for meta-discussion on the site itself.

founded 4 years ago
MODERATORS
 

Hopefully I'm not repeating an already known issue.

,,,,,,,,,,,

edit: just to clarify this particular sequence of events. It usually happens when I navigate into a post. And I stay there. And then later, sometimes even after leaving the window, and I come back and try to navigate back to the main page. The navigation is unresponsive. Then when I go to leave the hexbear website, it lets me but only after I "okay" a message that says, "Leave site? Your changes won't be saved".. so somehow the website thinks I am writing a comment even though that is not the case.

,,,,,,,,,,,

edit2: appears that these are the errors I am getting from within the console:

Failed to load resource: net::ERR_CONNECTION_CLOSED 2client.js?v=1:2 Uncaught TypeError: e is not a function at client.js?v=1:2:904615 at Array.forEach () at Object.call (client.js?v=1:2:904584) at C (client.js?v=1:2:909616) at Object.t [as push] (client.js?v=1:2:909921) at Object.Q [as event] (client.js?v=1:2:914009) at ae (client.js?v=1:2:210176) at HTMLDocument. (client.js?v=1:2:209738) client.js?v=1:2 Websocket closed. (anonymous) @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 e.dispatchEvent @ client.js?v=1:2 e.handleEvent @ client.js?v=1:2 handleCloseEvent @ client.js?v=1:2 client.js?v=1:2 WebSocket connection to 'wss://hexbear.net/api/v3/ws' failed: e.tryConnect @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 client.js?v=1:2 Websocket closed. (anonymous) @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 e.dispatchEvent @ client.js?v=1:2 e.handleEvent @ client.js?v=1:2 handleCloseEvent @ client.js?v=1:2 client.js?v=1:2 WebSocket connection to 'wss://hexbear.net/api/v3/ws' failed: e.tryConnect @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 client.js?v=1:2 Websocket closed.

,,,,,,,,,,,

I find that in certain situations, I cause my session with the website to freeze.

I am not certain what leads to this, but I think the cause has something to do with the fact that I've told Hex Bear I want to comment, or make some other edit on the current page. (From what I can ascertain though, I haven't intentionally gone into such an editing mode.)

The workaround is that I navigate away from the Hex Bear website, usually by doing a search for "hex bear". Then, I navigate back into a fresh Hex Bear session. When I do the first step above, I get this message, "Leave Site? Changes you made may not be saved." I click yes and that allows me to find Hex Bear and start my new session.

Just curious if anyone has encountered this? I am one of those end users who gets lost easily and thus causes mayhem to happen on occasion.

Thanks so much, if you want me to provide more detail, just holler...>

edit: it happened on the new megathread just now https://hexbear.net/post/276470 (The Einstein thread) my cursor wasn't focused on the comment field or anything I could tell. When I would go to click on the "hexbear" link at the top of the page there was no response. when I went to the url field and navigated away from the page, there was that message, "Leave Site? Changes you made may not be saved."

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here