I’ve had this issue as well, most frequently with a mac running Safari. I remember reading somewhere that this was a common thing with discord based forums and is at least partially due to flaky internet connections
I was wondering if that might be it. My cell service does fluctuate from time to time out here in the boondocks. Sounds like it might be timing out a little too hastily, typical of software written by those with unwaveringly good connections.
I have been updating Discourse regularly from its upgrades dashboard and generally multiple times throughout the week. It was just updated yesterday so the error could have been introduced in an update, or it could be ongoing. @Dellaster, when did this bug begin?
That’s an idea. This issue seems to stem more into server-client connections while the other issue seems to be more of an issue with read history (i.e. you should be directed to your last read post in a discussion), but timing could be the tell-all. If there is a common thread here, perhaps there could be an issue with how user data is sent and written to the backend database on the server where it is not reliably superseding or updating all older preexisting user data across all scopes and schemas? For example, the server might be properly marking down your last read post for the dividing line that @JoeS noted since its associated record is updated in the database, but it may not be fully committed across all areas of the forum’s backend database, such as the area of the database pertaining to the mechanism for indicating to the user’s browser to load directly on their last read post in that topic thread.
@JoeS, @Dellaster, @Desertlap, and anyone else who has hit this snag, could you visit TabletPCReview Forum and let me know if you can still reproduce the draft bug? The safe mode view is temporary and local to the tab session you do it in and is perfectly harmless. I need this done to rule out if it is Discourse or not. If you can’t reproduce the bug in safe mode, then it is a plug-in or theme component that is causing the issue which will require further digging.
Just realized, when you open a link in a background tab (ctrl-click), you’re out of safe mode, so that’s not a good way to test it. And even then the “scroll to wrong post bug” didn’t reproduce, take that as you will.
FWIW I’m using the “light” theme on all my devices, simply because I find it more pleasant to look at, but not customization or tweaks.
Also @Hifihedgehog definitely anecdotal, but I was unintentionally using private browsing in edge yesterday and I saw some odd cache and cookie behavior where they weren’t being updated/cleared like they should.
Can’t say for sure, if that has anything to do with anything but thought I’d pass it along