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 (<anonymous>) 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.<anonymous> (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."
It does seem like a distinct error, although it's possible it's linked to the same underlying issue. Ideally you'd be able to find a way of consistently reproducing the error, but it sounds like it may be time-dependent like the issue where if you leave a tab open long enough the post can change, which causes people to unknowingly comment on the wrong post. You could try to do something similar on an instance which is using an 18.x version of the UI like lemmy.world (that's the first one I found which reports its UI version) and see if you experience the bug or not.
Whenever you encounter a bug like this, it can be helpful for developers to see any errors from your browser's console (accessible using Shift+Ctrl+J on Chrome or Shift+Ctrl+K on Firefox). You'll want to make sure that your session token or anything like that isn't in there, but unless you're doing an action which requires authentication that shouldn't be an issue (if unsure you can always keep it in a text file locally and ask a developer what's okay to post).
Also (and this is a question to any web devs that might be reading), what's the easiest way as an end user to help with tracking down a JS bug when I'm being served minified JS but have access to the original JS? Google tells me intercepting the request with Fiddler is the way to go (might try to play around with it now), but I was curious to hear your opinions.
Great advice, I'll take a look at that Fiddler thingie. And the console procedure. Cheers.
deleted by creator
I wouldn't worry about Fiddler--the use case I mentioned is for if you want to dive in the code, not so much for general error reporting
BTW< hitting the page refresh button also brings up the "Leave Site" popup.
I believe this indicates that a
beforeunloadevent is being handled by something--ordinarily, you'd expect it to be an open editor box or some other kind of form, but it seems like it's being handled in error. If that's the case, this is a distinct bug: the editor error stems from a bug in how the UI blocks the user from leaving the page with unsaved data (correct action, incorrect implementation), but what you're describing is the browser improperly blocking navigation (incorrect action).Again, it's possible that the issue will have already been fixed in the newer version of the UI, so you could sit tight until Hexbear gets update and see if the bug is still present, but perhaps an actual dev can step in and ask more targeted questions to hone in on the source of the problem since it's not really my area of expertise.
undefined> sit tight until Hexbear gets update and see if the bug is still present, but perhaps an actual dev can step in and ask more targeted questions to hone in on the source of the problem since it's not really my area of expertise.
will do. thanks much!!!
I updated my post with the error messages from the console. I just copied and pasted from chrome console, directly into my post. If there is a more elegant way to do it, like a screen print perhaps....?
Just place ``` on a line by itself before and after your console log, which will make it monospace and preserve all whitespace like so:
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 (<anonymous>) 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.<anonymous> (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've seen people on Hexbear mention that WebSockets are the cause of a lot of the bugginess we experience and might be getting the boot, although I can't say for certain if that's the source of your issue (not really a webdev person myself).