新しいトピックに移動する際に、投稿履歴で20件前の投稿にジャンプする

[agemo]

Spotted it on Safari - iOS 14.x

[piffy]

I’ve been having this issue on my site lately, typically with larger topics that take longer to load.

Anyone else having a similar issue still. Could it be the race condition mentioned in the commit above?

[Sevencasper]

For some time (over 6 months) I have been having this problem and these issues also (using windows 11 and edge browser (Version 113.0.1774.42 (Official build) (64-bit)) :

The read post position changed in topic?

Hello Sam, No, after revert the commit it is good for me. The first thing I mentioned is probably not an issue As Jarek said this is how it works. I think I mixed up this with the logged out topic view? When I logged out It goes to the next post rather than the last onscreen post.

Bottom of topic shows "There is 1 unread remaining" when there are actually 0 unread topics remaining

I’ve reported this before too, but I was pointed to this post:

I initially thought it was from switching between my phone and pc but it continued after I stopped using the phone to access the forum.
I posted about it on the forum where it was occurring and it was suggested to try a different browser (der).

I have changed to Firefox browser (Version 113.0.1 64 bit) and all my issues with discourse forums have resolved.

[AzaB2C (Aza's Built to Code)]

Hello! Am visiting from the V1 Engineering Forum, several of us noticed this/similar unexpected behavior change.

Expected visiting a previously read topic to display the latest post read.
Actually seeing topics open 20 posts earlier. For Topics with less than 20 posts you end up positioned at the first post, and end up burning time scrolling down trying to figure which posts are newer than what you read last.

There an Admin setting to fix? And/or Discourse code fix available?

[Firepup650 (Firepup Sixfifty)]

This seems to have recently re-occured, and should be fixed soon (as the change was already merged)
New post:

Topics jumping to wrong post

Thanks so much for the clear reproduction steps @Don Yup, that’s it! Two things going on here at the same time Loading slider service needs to remove the still-loading class from the body LockOn needs to scroll to the right place They were both scheduled in the afterRender part of Ember’s runloop. And since the ‘lock on’ stuff is technically scheduled first, it was being run first. And so LockOn was running while all the post HTML was in the DOM, but still had display: none. …

GitHub PR:

FIX: Avoid scroll jumping for topics on slow connections

[JammyDodger]

Let’s close this one off in favour of the more recent one.