4chan-x
4chan-x copied to clipboard
ccd0
Thread watcher resetting to a previous state when I navigate to /r9k/
Submitter: Anonymous This is happening when I close all 4chan tabs and then go to /r9k/. My thread watcher is going back to the state it was in two days ago (at the time I'm writing this). Not only this but my replies in the threads I've posted in since then are not marked as "mine." It goes without saying that these threads also have disappeared from my thread watcher. I noticed that it resets to this same state, with the exact same threads and "read" states in the thread watcher, only when I open /r9k/ independent of other boards.
For example, if I have /ck/ open and I then open a new /r9k/ tab using the 4chanx page header, the thread watcher is unchanged from the /ck/ tab. However, if I open a new tab, then type the /r9k/ URL and press enter, this issue happens in the /r9k/ tab. The issue does not persist as long as I close the /r9k/ tab, but if I close the /ck/ tab and then close the /r9k/ tab, I noticed that no matter what board I open from this point, the thread watcher is reset to that previous point as I explained.
For what it's worth, this happens in more than just /r9k/. Happened to me while reloading /pol/ and /a/ before as well. Every time restarting my browser (Firefox 84.0.2) has fixed the issue, temporarily at least. This latest time it happened after my computer was woken up from sleep, not sure if that's relevant, though.
E: Just happened again after waking my computer up from sleep. Maybe something related to that, caching an old copy of the watched threads and then getting stuck with it? Restarting the browser still fixes. E2: Just happened without my computer sleeping, except this time it was every time I refreshed a specific thread, not a board.
Are you using the script with Greasemonkey or Violentmonkey or Tampermonkey or something else? I ask because it seems like something that could be a bug in that extension.
You might try seeing if installing a newer/older version of Violentmonkey helps.
from #2907:
Seemingly at random, the unread counter on the title sometimes does not update after scrolling past new posts. It however does update when I make a post. A normal refresh does not fix this but a cache-clear refresh does.
Compared to correctly working pages, the pages with this issue has the following in the console: Uncaught TypeError: Favicon.el is undefined update moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:22963 ready moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:22719 cb moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:5208 event moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:5220 initThread moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:27838 softTask moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:28054 callbackNodesDB moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:28060 initThread moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:27831 initReady moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:27793 cb moz-extension://c2e27c7e-387a-4aa9-a288-873556e119e2/ 4chan X.user.js#3:4797
Versions: Firefox 84, 4chan X 1.14.20.6, Violentmonkey 2.12.8
from #2918:
Submitter: Andrew A Brenton When I click on the thread watcher "eye" icon, it will have the same five pruned threads from a week ago, and will not update with threads that I have replied to. When I manually delete the pruned threads, and reload the page, the same five threads will reappear. When I click the "prune dead threads" box and reload, the box will still be unchecked.
gitdine replied:
I've also been experiencing for the past month or so. It has been accompanied by the unread reply favicon often failing to update when I scroll down, forcing me to reload the tab.
This is just a hunch, but I feel like 4chan X storage may somehow become corrupt upon updating to Violentmonkey 2.12.8, because that was around the time this issue appeared for me. And I doubt it's a Firefox/config issue because the same thing happens on Chromium with the same version Violentmonkey.
I've tried resetting/re-installing the script, which doesn't fix it. I might re-install Violentmonkey and report back.
So reinstalling Violentmonkey doesn't fix, nor does changing the injection mode.
However downgrading to Violentmonkey 2.12.7 seemingly does.
I've reproduced this issue across different profiles and browsers but only with Violentmonkey 2.12.8, Tampermonkey doesn't seem to be affected nor do older versions of Violentmonkey. The dev console throws the same Uncaught TypeError error message referenced above.
Still having this issue. Violentmonkeyv2.13.3 latest version of 4chan X Firefox 107.0
